91
edits
ReleaseEngineering/ThunderbirdTryServer: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/ThunderbirdTryServer (view source)
Revision as of 05:28, 16 May 2016
, 16 May 2016Update "pushing mozilla-central patches" about new findings
(→Pushing mozilla-central patches: - Brought up to date.) |
(Update "pushing mozilla-central patches" about new findings) |
||
| Line 27: | Line 27: | ||
There's two steps to this process. | There's two steps to this process. | ||
# Edit client.py-args: remove the hgtool options, add --apply-patches. | # Edit client.py-args: remove the --hgtool* options, add --apply-patches option. | ||
#* [[ReleaseEngineering/ThunderbirdTryServer/ApplyPatchesMozconfigPatch|Example patch here]] (Note: | #* [[ReleaseEngineering/ThunderbirdTryServer/ApplyPatchesMozconfigPatch|Example patch here]] (Note: Before November 2015 there was no --hgtool1 option in the file). | ||
#* If you do this as a separate patch in your Mecurial queue, you can reuse it whenever you want. Otherwise this change can go into the patch created in the step 4. | #* If you do this as a separate patch in your Mecurial queue, you can reuse it whenever you want. Otherwise this change can go into the patch created in the step 4. | ||
#* Note: hgtool option removal is because I'm not convinced if applying a patch affects the hg share or not. | #* Note: --hgtool option removal is because I'm not convinced if applying a patch affects the hg share or not. | ||
# Copy your mozilla-central patch to somewhere in your comm-central tree (it can be placed into the root directory) and name it something like: <code>mozilla-<anything>.patch</code> (the <code>mozilla-</code> prefix is essential). | # Copy your mozilla-central patch to somewhere in your comm-central tree (it can be placed into the root directory) and name it something like: <code>mozilla-<anything>.patch</code> (the <code>mozilla-</code> prefix is essential). | ||
# <code>hg add</code> your patch. | # <code>hg add</code> your patch. | ||
| Line 36: | Line 36: | ||
# Push your patches to try-comm-central. | # Push your patches to try-comm-central. | ||
The client.py code will automatically apply your patch when the code is checked out. Any apply failures will cause the builds to be aborted. | The client.py code will automatically apply your mozilla-central patch when the code is checked out. Any apply failures will cause the builds to be aborted. The mozilla-central patches are supposedly applied in the alphabetic order of their file names. You can mix comm-central and mozilla-central patches in the same batch being pushed. | ||
=== Pushing ldap/chatzilla/venkman/DOM Inspector patches === | === Pushing ldap/chatzilla/venkman/DOM Inspector patches === | ||