ReleaseEngineering/ThunderbirdTryServer: Difference between revisions

remove completely obsolete section about ldap/chatzilla/venkman/DOM Inspector patches
(Revise example try server syntax based on JorgK's comments)
(remove completely obsolete section about ldap/chatzilla/venkman/DOM Inspector patches)
Line 34: Line 34:


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>.
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>.
=== Pushing ldap/chatzilla/venkman/DOM Inspector patches ===
The mozilla build system also supports modifying code from other hg.mozilla.org code repositories for testing on the try server. The approach for this is basically the same as in the [[#Pushing_mozilla-central_patches|Pushing mozilla-central patches]] section, except the patch file name has to be <code>ldap-&lt;anything&gt;.patch</code>, <code>chatzilla-&lt;anything&gt;.patch</code>, <code>venkman-&lt;anything&gt;.patch</code> or <code>inspector-&lt;anything&gt;.patch</code> depending on what patch you want to test.
== Known issues ==
== Known issues ==


136

edits