.conffiles (even if the component is written in JS)
mozconfigfile and add these lines:
comm-centraltree. This might not be the one you expect.
Bto turn green, you don't need to wait for the tests) before building locally
B, and go down to the bottom of the Job Details tab:
hg update -r abcdef1234before building. In general, when a new build begins on the build infrastructure, it uses the latest mozilla-central as well as the latest comm-central, but that may no longer be the case by the time you build.
./mach build faster(or
../mach build -C . fasterif your current directory is comm-central). This skips a bunch of steps at the beginning and end of the build process that you might not need. When in doubt, don't build faster.
--artifactto your try syntax. For example:
macosx64in that case.)
defaultwith the revision you need. If you don't, the Try server will use the latest mozilla-central revision, which may or may not be the same one used for the latest comm-central build.