canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
ReleaseEngineering/ThunderbirdTryServer: Difference between revisions
ReleaseEngineering/ThunderbirdTryServer (view source)
Revision as of 09:16, 30 August 2012
, 30 August 2012→Tips and Tricks
(Created page with "== Basic Use == The Thunderbird try server works in exactly the same way to the Firefox try server with a few minor differences. The automation is based on the same hardware and...") |
|||
| Line 20: | Line 20: | ||
* Pushing a try build with try-comm-central will always pick the latest m-c changeset. | * Pushing a try build with try-comm-central will always pick the latest m-c changeset. | ||
=== Pushing mozilla-central patches === | |||
There's two steps to this process. | |||
# Edit the mozconfigs, remove the hgtool option, add --apply-patches | |||
#* Example patch here | |||
#* Do this as a separate item in your mq and you can use whenever you want | |||
#* Note: hgtool option removal is because I'm not convinced if applying a patch affects the hg share or not | |||
# Take your mozilla-central patch and name it something like: <code>mozilla-<anything>.patch</code> | |||
# <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 | |||
# 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. | |||
== Known issues == | == Known issues == | ||