ReleaseEngineering/ThunderbirdTryServer: Difference between revisions

Jump to navigation Jump to search
Remove buildbot content and clarify a few things
(Update download information for try builds.)
(Remove buildbot content and clarify a few things)
Line 21: Line 21:


In order for <code>../mach try <TryChooserSyntaxOptions></code> to work
In order for <code>../mach try <TryChooserSyntaxOptions></code> to work
* You must run <code>../mach try</code> from *within* <code>comm/</code>. Running <code>mach try</code> from the <code>mozilla-central</code> (sometimes named <code>source/</code>) folder will not work.
* You must run <code>../mach try</code> (note the two dots) from *within* <code>comm/</code>. Running <code>mach try</code> from the <code>mozilla-central</code> (sometimes named <code>source/</code>) directory will not work.
* The try syntax needs to include <code>--buildbot</code> to trigger buildbot builds. Without that option, TaskCluster builds are triggered.
* After running that command you should see: <code><nowiki>pushing to ssh://hg.mozilla.org/try</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]
* Finished builds can be accessed through treeherder. Click on the green B of the respective platform, then on the bottom click Job Details. In the list of artifact uploads, click the archive for your platform: Linux uses target.tar.bz2, OSX uses target.dmg, Windows uses target.zip
* Finished builds can be accessed through treeherder. Click on the green B of the respective platform, then on the bottom click Job Details. In the list of artifact uploads, click the archive for your platform: Linux uses target.tar.bz2, OSX uses target.dmg, Windows uses target.zip
Line 32: Line 31:


=== Pushing mozilla-central patches ===
=== Pushing mozilla-central patches ===
== For Buildbot builds ==
There's two steps to this process.
# Add --apply-patches to build/client.py-args.
#* [[ReleaseEngineering/ThunderbirdTryServer/ApplyPatchesMozconfigPatch|Example patch here]].
#* 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.
# 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-&lt;anything&gt;.patch</code> (the <code>mozilla-</code> prefix is essential).
# <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 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 ==
== 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>.
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>.
52

edits

Navigation menu