ReleaseEngineering/ThunderbirdTryServer: Difference between revisions

Clarify instructions for pushing mozilla-central patches
(→‎Tips and Tricks: add examples of basic try runs to start with)
(Clarify instructions for pushing mozilla-central patches)
Line 34: Line 34:
=== Pushing mozilla-central patches ===
=== Pushing mozilla-central patches ===


== For TaskCluster builds ==
For TaskCluster builds, 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>.
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 ===
52

edits