Name Description Size Coverage
afl-nyx.patch 619 -
android-gradle-dependencies -
android-gradle-dependencies.sh 348 -
android-xmlstarlet.sh 186 -
browsertime.sh 372 -
build-7zz.sh 745 -
build-afl.sh 1054 -
build-binutils-linux.sh 297 -
build-breakpad-injector.sh 569 -
build-cabextract.sh 355 -
build-cctools-port.sh 4487 -
build-clang-mingw.sh 7809 -
build-clang-tidy-external.sh 330 -
build-clang.sh 1862 -
build-cmake.sh 2857 -
build-compiler-rt-wasi.sh 1040 -
build-compiler-rt.sh 765 -
build-cpython.sh 5287 -
build-custom-car.sh 9684 -
build-custom-v8.sh 1088 -
build-dist-toolchains.sh 370 -
build-dmg-hfsplus.sh 1265 -
build-dxc.sh 2772 -
build-gcc-linux.sh 505 -
build-gcc-sixgill-plugin-linux.sh 1989 -
build-geckodriver.sh 2576 -
build-gn-common.sh 839 -
build-gn-linux.sh 205 -
build-gn-macosx.sh 1155 -
build-gn-win64.sh 380 -
build-hfsplus-linux.sh 302 -
build-libunwind.sh 537 -
build-libxml2.sh 2005 -
build-llvm-common.sh 5874 -
build-llvm-symbolizer.sh 91 -
build-mar-tools.sh 500 -
build-mingw-fxc2-x86.sh 422 -
build-mingw32-nsis.sh 2295 -
build-mkbom-linux.sh 344 -
build-mozmake.sh 1386 -
build-msix-packaging.sh 1220 -
build-nasm.sh 1670 -
build-nodejs.sh 1146 -
build-nsis.sh 783 -
build-onnxruntime.sh 6218 -
build-pkgconf.sh 1229 -
build-profiler-node-tools.sh 424 -
build-python-wheel.sh 1450 -
build-rust-based-toolchain.sh 4350 -
build-sysroot-wasi.sh 1608 -
build-sysroot.sh 3878 -
build-upx.sh 643 -
build-winchecksec.sh 7641 -
build-WindowsAppSDK.sh 874 -
build-wine.sh 640 -
build-xar-linux.sh 710 -
build-xz.sh 631 -
build-zucchini.sh 1254 -
cargo-apk-Cargo.lock 19922 -
cctools-ld64-dead-strip-compiler-builtins.patch 1008 -
check-vendor-coverage.py Check every vendored moz.yaml is verified by a vendor-verify task. Turns the tree orange if a vendored moz.yaml (has a `vendoring:` section, non-rust) is not in any task's `members` in vendor-verify.yml -- so a newly added vendored library can't silently escape the re-vendoring checks. Also flags stale entries, in `members` or in the expected-fail annotations, whose moz.yaml no longer exists or is no longer vendored. Run as a source-test task gated on moz.yaml + config changes. 3935 -
eslint-plugin-mozilla.sh 493 -
fetch-cft-chromedriver.py This script downloads chromedriver for a given platform and then packages the driver along with the revision and uploads the archive. This is currently accomplished by using "last known good version" of the chromedrivers associated with Chrome for Testing. The `Canary` channel is specified as it is required for the Chromium-as-Release performance tests. 9471 -
fetch-chromium.py This script downloads the latest chromium build (or a manually defined version) for a given platform. It then uploads the build, with the revision of the build stored in a REVISION file. 6727 -
fetch-onnxruntime-deps.sh 2348 -
fetch-talos-pdfs.py This script downloads all the required PDFs from the test_manifest.json file found in the mozilla pdf.js repo. 4126 -
generic-node-modules.sh 345 -
get-hostutils.sh 267 -
get_vs.py 4310 -
libtapi.patch 731 -
mingw-dispatchqueue.patch 7495 -
mingw-dwrite_3.patch 7198 -
mingw-enum.patch 921 -
mingw-foundation_redef.patch 7839 -
mingw-ts_sd.patch 840 -
mingw-widl.patch 1097 -
moz.build 311 -
node-modules.sh 381 -
onnxruntime.patches -
pack-cpython.sh 891 -
pack.sh 443 -
private_local_toolchain.sh 228 -
puppeteer-build.sh 740 -
repack-android-avd-linux.sh 744 -
repack-android-avd-macos.sh 583 -
repack-android-emulator-linux.sh 1067 -
repack-android-ndk-linux.sh 546 -
repack-android-sdk-linux.sh 733 -
repack-android-sdk-macos.sh 572 -
repack-android-simpleperf-linux.sh 897 -
repack-android-system-images-linux.sh 554 -
repack-android-system-images-macos.sh 617 -
repack-clang.sh 1571 -
repack-jdk-linux.sh 347 -
repack-jdk-macos.sh 352 -
repack-node.sh 416 -
repack-rust-analyzer.sh 419 -
repack_rust.py This script downloads and repacks official rust language builds with the necessary tool and target support for the Firefox build environment. 26298 -
run-fetch-talos-pdfs.sh 243 -
run-profileserver-macos.sh 591 -
run-profileserver.sh 1011 -
source-test-clang-setup.sh 1071 -
source-test-common.sh 468 -
source-test-infer-setup.sh 771 -
stylelint-plugin-mozilla.sh 517 -
summarize-tgdiff.py 1465 -
terser.sh 410 -
tooltool-download.sh 623 -
unify.sh 1867 -
unpack-sdk.py 3790 -
vendor-verify-expected-fail.yml 2113 -
verify-devtools-bundle.py Check that the current sourcemap and worker bundles built for DevTools are up to date. This job should fail if any file impacting the bundle creation was modified without regenerating the bundles. This check should be run after building the bundles via: cd devtools/client/debugger yarn && node bin/bundle.js Those steps are done in the devtools-verify-bundle job, prior to calling this script. The script will only run `hg status devtools/` and check that no change is detected by mercurial. 2359 -
verify-vendored-library.py Verify that re-vendoring a library reproduces what is committed. For each moz.yaml given, re-vendors it at the revision pinned in its moz.yaml (`./mach vendor <moz.yaml> -r <rev> --patch-mode check --force`) and confirms the result exactly matches what is committed. This catches changes to a vendored library (its sources or its patches) that were not re-vendored properly. Libraries listed in the `expected-fail` file passed with --expected-fail are inverted: they are known not to re-vendor cleanly yet, so a failure is expected (and green). If such a library starts reproducing cleanly, the job goes orange with an UNEXPECTED-PASS, forcing removal of the annotation -- after which it is a hard green requirement and can't silently regress. The whole working tree is restored between libraries, because some libraries (e.g. libvpx) write files outside their own vendor-directory, so a per-directory restore would leak into the next library's check. Note on `./mach vendor ... --patch-mode check` exit codes: they are inverted for our purposes -- 254 (from spurious_check's sys.exit(-2)) means the re-vendored result matched, and 0 means it differed and left the tree dirty. So the reliable signal is whether the working directory is clean afterwards; the exit code only distinguishes "matched" (254) from "errored before re-vendoring finished" (anything else) when the tree is clean. Usage: ./mach python taskcluster/scripts/misc/verify-vendored-library.py \\ [--expected-fail vendor-verify-expected-fail.yml] path/to/moz.yaml \\ [path/to/other/moz.yaml ...] 14822 -
vs-cleanup.sh 567 -
vs-setup.sh 2222 -
wasi-sdk.patch 4563 -
wr-cargotest-macos-build.sh 732 -
wr-macos-cross-build-setup.sh 2985 -
wrench-android-build.sh 850 -
wrench-deps-vendoring.sh 680 -
wrench-macos-build.sh 2180 -
wrench-windows-tests.sh 1130 -
zstdpy 2211 -