ReleaseEngineering/Buildbot Migration: Difference between revisions

(→‎Current state: current migration status)
(→‎Current state: we're done!)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Current state ==
Unless otherwise stated, assume builds/tests are running in buildbot.


{| class="wikitable"
|-
! Build / test name !! in buildbot? !! In taskcluster?
|-
| Firefox Linux 32/64 debug || no || yes (tier-1)
|-
| Firefox Linux 32/64 opt || no || yes (tier-1)
|-
| Firefox Linux (everything else) || no || yes
|-
| Firefox OSX64 debug || yes || yes (tier-2)
|-
| Firefox OSX (everything else) || yes || no
|-
| Firefox Windows (all) || yes || some (tier-3)
|}
== How do I find where a build/test job is running? ==
The best approach is the examine the job on [https://treeherder.mozilla.org treeherder]. Click on the job you're interested in, and look at the information on the bottom-left. Taskcluster jobs have [TC] in their name. They also have "Machine: unknown". Buildbot jobs have specific machine names specified, e.g. "Machine: bld-linux64-spot-134"
== Relevant source repositories ==
Buildbot jobs are defined in a pair of repositories:
* [https://hg.mozilla.org/build/buildbot-configs buildbot-configs]
* [https://hg.mozilla.org/build/buildbotcustom buildbotcustom]
Taskcluster jobs are mostly defined all in-tree:
* [https://hg.mozilla.org/mozilla-central/file/default/testing/taskcluster in-tree taskcluster configs]*

Latest revision as of 21:41, 19 November 2018