316
edits
ReleaseEngineering/ThunderbirdTryServer: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/ThunderbirdTryServer (view source)
Revision as of 21:24, 14 March 2018
, 14 March 2018Added section on how to push M-C patches in a C-C try using TaskCluster
(Better information on --buildbot) |
(Added section on how to push M-C patches in a C-C try using TaskCluster) |
||
| Line 15: | Line 15: | ||
These are the differences for the Thunderbird try server: | These are the differences for the Thunderbird try server: | ||
* The try syntax needs to include <code>--buildbot</code> to trigger buildbot builds. Without that option, TaskCluster builds are triggered | * The try syntax needs to include <code>--buildbot</code> to trigger buildbot builds. Without that option, TaskCluster builds are triggered. | ||
* Patches should be pushed to <code><nowiki>ssh://hg.mozilla.org/try-comm-central</nowiki></code> | * Patches should be pushed to <code><nowiki>ssh://hg.mozilla.org/try-comm-central</nowiki></code> | ||
* Results go to the [https://treeherder.mozilla.org/#/jobs?repo=try-comm-central try-comm-central on treeherder] | * Results go to the [https://treeherder.mozilla.org/#/jobs?repo=try-comm-central try-comm-central on treeherder] | ||
| Line 25: | Line 25: | ||
=== Pushing mozilla-central patches === | === Pushing mozilla-central patches === | ||
== For Buildbot builds == | |||
There's two steps to this process. | There's two steps to this process. | ||
| Line 37: | Line 38: | ||
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. | 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. | ||
== For TaskCluster builds == | |||
The process described above of applying M-C patches to C-C try pushes does not work for TaskCluster builds. For those, modify the <code>payload</code> section in the top-level <code>.taskcluster.yml</code> and point <code>GECKO_HEAD_REPOSITORY</code> to <code> https://hg.mozilla.org/try</code> and also modify <code>GECKO_HEAD_REF</code> to point to the changeset you previously pushed to M-C's try with <code>mach try empty</code>. | |||
=== Pushing ldap/chatzilla/venkman/DOM Inspector patches === | === Pushing ldap/chatzilla/venkman/DOM Inspector patches === | ||