Continuous Integration
taskcluster and treeherder taskcluster, mozilla's continuous integration (ci) system picks up changes pushed to hg.
... the results of taskcluster jobs (both builds and tests) are displayed in treeherder.
... there is a group of individuals who are constantly monitoring treeherder, looking for broken builds and/or tests.
...And 8 more matches

Old Thunderbird build
for hg tip, you should see green bs on https://treeherder.mozilla.org/#/jobs?repo=comm-central to start the build, cd into the comm-central subdirectory, and run: ./mozilla/mach build mach is our command-line tool to streamline common developer tasks.
... have you: check comm-central on treeherder for known failures at the time you pulled the code.

Simple Thunderbird build
for hg tip, you should see green bs on https://treeherder.mozilla.org/#/jobs?repo=comm-central to start the build, cd into the source directory, and run: ./mach build mach is our command-line tool to streamline common developer tasks.
... have you: check comm-central on treeherder for known failures at the time you pulled the code.

Running Automated JavaScript Tests
stests also runs on browser, with the following command: ./mach jstestbrowser to run specific test, you can use --filter=pattern command-line argument, where pattern is a regexp pattern that is tested against file:///{path_to_obj_dir}/dist/test-stage/jsreftest/tests/jsreftest.html?test={relative_path_to_test_from_js/src/tests} string: ./mach jstestbrowser --filter=pattern running jstests on treeherder when viewing treeherder after a push to the mozilla repositories, jstests run in the browser are shown as r(j) meaning "javascript reftests".
... running jit-tests on treeherder when viewing treeherder after a push to the mozilla repositories, jit-tests are run by calling make check, and appear under b.

Task graph
after a change to the gecko source code is pushed to version-control, jobs for that change appear on treeherder.
... the result of each task is sent to treeherder where developers and sheriffs can track the status of the push.

jpm - Archive of obsolete content
specify --stop-on-error to stop running tests after the first failure: jpm test --stop-on-error --tbpl print test output in treeherder format --times number run tests number of times: jpm test --times 2 -v --verbose verbose operation.

ESLint
it also runs on treeherder for every check-in.

Developer guide
treeherder treeherder shows the status of the tree (whether or not it currently builds successfully).

GC and CC logs
to find the cc logs once the try run has finished, click on the particular job, then click on "job details" in the bottom pane in treeherder, and you should see download links.

Profiling with the Firefox Profiler
symbols for try builds are not uploaded to the symbol server automatically, you need to trigger a "sym" job on treeherder: using treeherder's add new jobs ui, schedule a "sym" job for each platform whose "b" job you want symbols for.

Index
539 spidermonkey releases spidermonkey the easiest way to fetch the version corresponding to the current firefox release is to visit the treeherder page for the release repository and click on the first sm(pkg) link you see.

SpiderMonkey 52
you can download full source code from treeherder, by going to the mozilla-esr52 repository and clicking on the first sm(pkg) link you see.

SpiderMonkey releases
the easiest way to fetch the version corresponding to the current firefox release is to visit the treeherder page for the release repository and click on the first sm(pkg) link you see.

Web Replay
on treeherder, web replay tests currently only run on macos opt builds, and are prefixed with browser_dbg_rr.

Mozilla
supported build targets page moved to the in-tree documentation: https://firefox-source-docs.mozilla.org/build/buildsystem/supported-configurations.html task graph after a change to the gecko source code is pushed to version-control, jobs for that change appear on treeherder.