316
edits
ReleaseEngineering/ThunderbirdTryServer: Difference between revisions
ReleaseEngineering/ThunderbirdTryServer (view source)
Revision as of 11:25, 23 November 2015
, 23 November 2015→Pushing mozilla-central patches: - Brought up to date.
(→Differences: nowiki) |
(→Pushing mozilla-central patches: - Brought up to date.) |
||
| 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 | # Edit client.py-args: remove the hgtool options, add --apply-patches. | ||
#* [[ReleaseEngineering/ThunderbirdTryServer/ApplyPatchesMozconfigPatch|Example patch here]] | #* [[ReleaseEngineering/ThunderbirdTryServer/ApplyPatchesMozconfigPatch|Example patch here]] (Note: This is outdated, as of November 2015 you need to replace --hgtool=../tools/buildfarm/utils/hgtool.py and --hgtool1=../scripts/buildfarm/utils/hgtool.py). | ||
#* | #* 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). | ||
# <code>hg add</code> your patch | # <code>hg add</code> your patch. | ||
# Then <code>hg commit</code> your changes, or use <code>hg qnew</code> for a new item on your patch queue | # Then <code>hg commit</code> your changes, or use <code>hg qnew</code> for a new item on your patch queue. | ||
# 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 patch when the code is checked out. Any apply failures will cause the builds to be aborted. | ||