kinds.rst (28581B)
1 Task Kinds 2 ========== 3 4 This section lists and documents the available task kinds. 5 6 build 7 ----- 8 9 Builds are tasks that produce an installer or other output that can be run by 10 users or automated tests. This is more restrictive than most definitions of 11 "build" in a Mozilla context: it does not include tasks that run build-like 12 actions for static analysis or to produce instrumented artifacts. 13 14 build-extensions 15 ---------------- 16 17 Builds Firefox extensions with `mach build`. 18 19 build-fat-aar 20 ------------- 21 22 Build architecture-independent GeckoView AAR (Android ARchive) files. This build-like tasks is an 23 artifact build (ARMv7, but this is arbitrary) that itself depends on arch-specific Android build 24 jobs. It fetches arch-specific AAR files, extracts arch-specific libraries and preference files, 25 and then assembles a multi-architecture "fat AAR". Downstream consumers are expected to use 26 per-ABI feature splits to produce arch-specific APKs. 27 28 If you want to run this task locally, you need to specify these environment variable: 29 - MOZ_ANDROID_FAT_AAR_ARCHITECTURES: must be a comma-separated list of architecture. 30 Eg: "armeabi-v7a,arm64-v8a,x86_64". 31 - each of MOZ_ANDROID_FAT_AAR_ARM64_V8A, MOZ_ANDROID_FAT_AAR_ARMEABI_V7A, 32 and MOZ_ANDROID_FAT_AAR_X86_64 must be a path relative to MOZ_FETCHES_DIR. 33 34 build-signing 35 ------------- 36 37 Many builds must be signed. The build-signing task takes the unsigned `build` 38 kind artifacts and passes them through signingscriptworker to a signing server 39 and returns signed results. 40 41 build-mac-signing 42 ----------------- 43 44 Mac signing without notarization. 45 46 Uses a self-signed certificate on level 1 environments. 47 48 Shippable downstream tasks should use artifacts from build-mac-notarization. 49 50 build-mac-notarization 51 ---------------------- 52 53 Mac notarization on signingscript (linux) using rcodesign. 54 55 Only available in production environments, as Apple doesn't offer a test 56 endpoint for notarizing apps. 57 58 Downstream tasks switch to build-mac-signing in non-shippable builds or level 1 59 environments. 60 61 artifact-build 62 -------------- 63 64 This kind performs an artifact build: one based on precompiled binaries 65 discovered via the TaskCluster index. This task verifies that such builds 66 continue to work correctly. 67 68 bootstrap 69 --------- 70 71 This kind performs a standalone bootstrap of a Firefox build from various system environments. 72 73 hazard 74 ------ 75 76 Hazard builds are similar to "regular' builds, but use a compiler extension to 77 extract a bunch of data from the build and then analyze that data looking for 78 hazardous behaviors. 79 80 l10n 81 ---- 82 83 The l10n kind repacks a build (from the same source) for a subset of locales, 84 to exercise the localized repack logic in CI. 85 86 shippable-l10n 87 -------------- 88 89 The nightly l10n kind repacks a shippable build (from the same source code) 90 in order to provide localized versions of the same source. 91 92 shippable-l10n-signing 93 ---------------------- 94 95 The shippable l10n signing kind takes artifacts from the shippable-l10n kind and 96 passes them to signing servers to have their contents signed appropriately, based 97 on an appropriate signing format. One signing job is created for each shippable-l10n 98 job (usually chunked). 99 100 shippable-l10n-mac-signing 101 -------------------------- 102 103 Mac signing without notarization. 104 105 Uses a self-signed certificate on level 1 environments. 106 107 Shippable downstream tasks should use artifacts from build-mac-notarization. 108 109 shippable-l10n-mac-notarization 110 ------------------------------- 111 112 Mac notarization on signingscript (linux) using rcodesign. 113 114 Only available in production environments, as Apple doesn't offer a test 115 endpoint for notarizing apps. 116 117 Downstream tasks switch to build-mac-signing in non-shippable builds or level 1 118 environments. 119 120 source-test 121 ----------- 122 123 Source-tests are tasks that run directly from the Gecko source. This can include linting, 124 unit tests, source-code analysis, or measurement work. While source-test tasks run from 125 a source checkout, it is still possible for them to depend on a build artifact, though 126 often they do not. 127 128 code-review 129 ----------- 130 131 Publish issues found by source-test tasks on Phabricator. 132 This is a part of Release Management code review Bot. 133 134 upload-symbols 135 -------------- 136 137 Upload-symbols tasks run after builds and upload the symbols files generated by 138 build tasks to Socorro for later use in crash analysis. 139 140 upload-symbols-dummy 141 -------------------- 142 143 Upload-symbols-dummy ensures both x64 and macosx64 tasks run for nightlies and releases. 144 145 upload-generated-sources 146 ------------------------ 147 148 Upload-generated-sources tasks run after builds and upload source files that were generated as part of the build process to an s3 bucket for later use in links from crash reports or when debugging shipped builds. 149 150 upload-generated-sources-dummy 151 ------------------------------ 152 153 Upload-generated-sources-dummy ensures both x64 and macosx64 tasks run for nightlies and releases. 154 155 valgrind 156 -------- 157 158 Valgrind tasks produce builds instrumented by valgrind. 159 160 searchfox 161 --------- 162 163 Searchfox builds generate C++ index data for Searchfox. 164 165 static-analysis-autotest 166 ------------------------ 167 168 Static analysis autotest utility in order to be sure that there is no regression 169 when upgrading utilities that impact static-analysis. 170 171 toolchain 172 --------- 173 174 Toolchain builds create the compiler toolchains used to build Firefox. These 175 will eventually be dependencies of the builds themselves, but for the moment 176 are run manually via try pushes and the results uploaded to tooltool. 177 178 toolchain-dxc-upload 179 -------------------- 180 181 Upload Windows symbols for `DirectXShaderCompiler` to tecken, based on builds in `toolchain-dxc`. 182 Maintained by Firefox's WebGPU team. 183 184 spidermonkey 185 ------------ 186 187 Spidermonkey tasks check out the full gecko source tree, then compile only the 188 spidermonkey portion. Each task runs specific tests after the build. 189 190 mochitest 191 --------- 192 193 See the :doc:`test kind documentation <kinds/test>` for more info. 194 195 .. toctree:: 196 :hidden: 197 198 kinds/test 199 200 201 reftest 202 ------- 203 204 See the :doc:`test kind documentation <kinds/test>` for more info. 205 206 .. toctree:: 207 :hidden: 208 209 kinds/test 210 211 212 browsertime 213 ----------- 214 215 See the :doc:`test kind documentation <kinds/test>` for more info. 216 217 .. toctree:: 218 :hidden: 219 220 kinds/test 221 222 223 web-platform-tests 224 ------------------ 225 226 See the :doc:`test kind documentation <kinds/test>` for more info. 227 228 .. toctree:: 229 :hidden: 230 231 kinds/test 232 233 234 test 235 ---- 236 237 See the :doc:`test kind documentation <kinds/test>` for more info. 238 239 .. toctree:: 240 :hidden: 241 242 kinds/test 243 244 245 docker-image 246 ------------ 247 248 Tasks of the ``docker-image`` kind build the Docker images in which other 249 Docker tasks run. 250 251 The tasks to generate each docker image have predictable labels: 252 ``docker-image-<name>``. 253 254 Docker images are built from subdirectories of ``taskcluster/docker``, using 255 ``docker build``. There is currently no capability for one Docker image to 256 depend on another in-tree docker image, without uploading the latter to a 257 Docker repository. 258 259 balrog 260 ------ 261 262 Balrog tasks are responsible for submitting metadata to our update server (Balrog). 263 They are typically downstream of a beetmover job that moves signed MARs somewhere 264 (eg: beetmover and beetmover-l10n for releases, beetmover-repackage for nightlies). 265 266 beetmover 267 --------- 268 269 Beetmover, takes specific artifacts, "Beets", and pushes them to a location outside 270 of Taskcluster's task artifacts, (archive.mozilla.org as one place) and in the 271 process determines the final location and a "pretty" name (versioned product name) 272 273 beetmover-integration 274 --------------------- 275 Beetmover, takes specific artifacts, "Beets", and pushes them to a location outside 276 of Taskcluster's task artifacts, (archive.mozilla.org as one place) and in the 277 process determines the final location and a "pretty" name (versioned product name) 278 This separate kind archives builds from the autoland branch. 279 280 beetmover-l10n 281 -------------- 282 283 Beetmover L10n, takes specific artifacts, "Beets", and pushes them to a location outside 284 of Taskcluster's task artifacts, (archive.mozilla.org as one place) and in the 285 process determines the final location and a "pretty" name (versioned product name) 286 This separate kind uses logic specific to localized artifacts, such as including 287 the language in the final artifact names. 288 289 beetmover-repackage 290 ------------------- 291 292 Beetmover-repackage is beetmover but for tasks that need an intermediate step 293 between signing and packaging, such as OSX. For more details see the definitions 294 of the Beetmover kind above and the repackage kind below. 295 296 release-beetmover-push-to-release 297 --------------------------------- 298 299 release-beetmover-push-to-release publishes promoted releases from the 300 candidates directory to the release directory. This is part of release 301 promotion. 302 303 beetmover-source 304 ---------------- 305 Beetmover-source publishes release source. This is part of release promotion. 306 307 beetmover-geckoview 308 ------------------- 309 Beetmover-geckoview publishes the Android library called "geckoview". 310 311 beetmover-apt 312 ------------------- 313 Beetmover-apt publishes Linux .deb packages from the Mozilla archive to our APT repositories. 314 315 beetmover-rpm 316 ------------------- 317 Beetmover-rpm publishes Linux .rpm packages from the Mozilla archive to our RPM repositories. 318 319 beetmover-repackage-rpm 320 ----------------------- 321 Beetmover-repackage-rpm publishes Linux .rpm packages (main package and all langpacks) to the candidates directory. 322 323 condprof 324 -------- 325 condprof creates and updates realistic profiles. 326 327 release-source-checksums-signing 328 -------------------------------- 329 release-source-checksums-signing take as input the checksums file generated by 330 source-related beetmover task and sign it via the signing scriptworkers. 331 Returns the same file signed and additional detached signature. 332 333 beetmover-checksums 334 ------------------- 335 Beetmover, takes specific artifact checksums and pushes it to a location outside 336 of Taskcluster's task artifacts (archive.mozilla.org as one place) and in the 337 process determines the final location and "pretty" names it (version product name) 338 339 release-beetmover-source-checksums 340 ---------------------------------- 341 Beetmover, takes source specific artifact checksums and pushes it to a location outside 342 of Taskcluster's task artifacts (archive.mozilla.org as one place) and in the 343 process determines the final location and "pretty" names it (version product name) 344 345 perftest 346 -------- 347 Runs performance tests using mozperftest. 348 349 release-balrog-submit-toplevel 350 ------------------------------ 351 Toplevel tasks are responsible for submitting metadata to Balrog that is not specific to any 352 particular platform+locale. For example: fileUrl templates, versions, and platform aliases. 353 354 Toplevel tasks are also responsible for updating test channel rules to point at the Release 355 being generated. 356 357 release-secondary-balrog-submit-toplevel 358 ---------------------------------------- 359 Performs the same function as `release-balrog-submit-toplevel`, but against the beta channel 360 during RC builds. 361 362 release-balrog-scheduling 363 ------------------------- 364 Schedules a Release for shipping in Balrog. If a `release_eta` was provided when starting the Release, 365 it will be scheduled to go live at that day and time. 366 367 release-secondary-balrog-scheduling 368 ----------------------------------- 369 Performs the same function as `release-balrog-scheduling`, except for the beta channel as part of RC 370 Releases. 371 372 release-binary-transparency 373 --------------------------- 374 Binary transparency creates a publicly verifiable log of binary shas for downstream 375 release auditing. https://wiki.mozilla.org/Security/Binary_Transparency 376 377 release-flatpak-push 378 -------------------- 379 Pushes Flatpak repackage on Flathub 380 381 release-secondary-flatpak-push 382 ------------------------------ 383 Performs the same function as `release-flatpak-push`, except for the beta channel as part of RC 384 Releases. 385 386 release-notify-av-announce 387 -------------------------- 388 Notify anti-virus vendors when a release is likely shipping. 389 390 release-notify-push 391 ------------------- 392 Notify when a release has been pushed to CDNs. 393 394 release-notify-ship 395 ------------------- 396 Notify when a release has been shipped. 397 398 release-secondary-notify-ship 399 ----------------------------- 400 Notify when an RC release has been shipped to the beta channel. 401 402 release-notify-promote 403 ---------------------- 404 Notify when a release has been promoted. 405 406 release-notify-started 407 ---------------------- 408 Notify when a release has been started. 409 410 release-notify-testrail 411 ----------------------- 412 Create milestones in testrail for the next fenix/focus releases, and send a slack notification. 413 414 release-bouncer-sub 415 ------------------- 416 Submits bouncer information for releases. 417 418 release-mark-as-shipped 419 ----------------------- 420 Marks releases as shipped in Ship-It v1 421 422 release-bouncer-aliases 423 ----------------------- 424 Update Bouncer's (download.mozilla.org) "latest" aliases. 425 426 cron-bouncer-check 427 ------------------ 428 Checks Bouncer (download.mozilla.org) uptake. 429 430 bouncer-locations 431 ----------------- 432 Updates nightly bouncer locations for version bump. 433 434 release-bouncer-check 435 --------------------- 436 Checks Bouncer (download.mozilla.org) uptake as part of the release tasks. 437 438 release-generate-checksums 439 -------------------------- 440 Generate the per-release checksums along with the summaries 441 442 release-generate-checksums-signing 443 ---------------------------------- 444 Sign the pre-release checksums produced by the above task 445 446 release-generate-checksums-beetmover 447 ------------------------------------ 448 Submit to S3 the artifacts produced by the release-checksums task and its signing counterpart. 449 450 release-final-verify 451 -------------------- 452 Verifies the contents and package of release update MARs. 453 454 release-secondary-final-verify 455 ------------------------------ 456 Verifies the contents and package of release update MARs for RC releases. 457 458 release-push-langpacks 459 ------------------------------- 460 Publishes language packs onto addons.mozilla.org. 461 462 release-beetmover-signed-langpacks 463 ---------------------------------- 464 Publishes signed langpacks to archive.mozilla.org 465 466 release-beetmover-signed-langpacks-checksums 467 -------------------------------------------- 468 Publishes signed langpacks to archive.mozilla.org 469 470 release-update-verify 471 --------------------- 472 Verifies the contents and package of release update MARs. 473 release-secondary-update-verify 474 ------------------------------- 475 Verifies the contents and package of release update MARs. 476 477 release-update-verify-next 478 -------------------------- 479 Verifies the contents and package of release and updare MARs from the previous ESR release. 480 481 release-update-verify-config 482 ---------------------------- 483 Creates configs for release-update-verify tasks 484 485 release-secondary-update-verify-config 486 -------------------------------------- 487 Creates configs for release-secondary-update-verify tasks 488 489 release-update-verify-config-next 490 --------------------------------- 491 Creates configs for release-update-verify-next tasks 492 493 release-updates-builder 494 ----------------------- 495 Top level Balrog blob submission & patcher/update verify config updates. 496 497 release-version-bump 498 -------------------- 499 Bumps to the next version. 500 501 release-source 502 -------------- 503 Generates source for the release 504 505 release-source-signing 506 ---------------------- 507 Signs source for the release 508 509 release-partner-repack 510 ---------------------- 511 Generates customized versions of releases for partners. 512 513 release-partner-attribution 514 --------------------------- 515 Generates attributed versions of releases for partners. 516 517 release-partner-repack-chunking-dummy 518 ------------------------------------- 519 Chunks the partner repacks by locale. 520 521 release-partner-repack-signing 522 ------------------------------ 523 Internal signing of partner repacks. 524 525 release-partner-repack-mac-signing 526 ---------------------------------- 527 528 Mac signing without notarization. 529 530 Uses a self-signed certificate on level 1 environments. 531 532 Shippable downstream tasks should use artifacts from build-mac-notarization. 533 534 release-partner-repack-mac-notarization 535 --------------------------------------- 536 537 Mac notarization on signingscript (linux) using rcodesign. 538 539 Only available in production environments, as Apple doesn't offer a test 540 endpoint for notarizing apps. 541 542 Downstream tasks switch to build-mac-signing in non-shippable builds or level 1 543 environments. 544 545 release-partner-repack-repackage 546 -------------------------------- 547 Repackaging of partner repacks. 548 549 release-partner-repack-repackage-signing 550 ---------------------------------------- 551 External signing of partner repacks. 552 553 release-partner-repack-beetmover 554 -------------------------------- 555 Moves the partner repacks to S3 buckets. 556 557 release-partner-attribution-beetmover 558 ------------------------------------- 559 Moves the partner attributions to S3 buckets. 560 561 release-partner-repack-bouncer-sub 562 ---------------------------------- 563 Sets up bouncer products for partners. 564 565 release-early-tagging 566 --------------------- 567 Utilises treescript to perform tagging that should happen near the start of a release. 568 569 release-eme-free-repack 570 ----------------------- 571 Generates customized versions of releases for eme-free repacks. 572 573 release-eme-free-repack-signing 574 ------------------------------- 575 Internal signing of eme-free repacks 576 577 release-eme-free-repack-repackage 578 --------------------------------- 579 Repackaging of eme-free repacks. 580 581 release-eme-free-repack-repackage-signing 582 ----------------------------------------- 583 External signing of eme-free repacks. 584 585 release-eme-free-repack-beetmover 586 --------------------------------- 587 Moves the eme-free repacks to S3 buckets. 588 589 release-eme-free-repack-beetmover-checksums 590 ------------------------------------------- 591 Moves the beetmover checksum for eme-free repacks to S3 buckets. 592 593 release-eme-free-repack-mac-signing 594 ----------------------------------- 595 596 Mac signing without notarization. 597 598 Uses a self-signed certificate on level 1 environments. 599 600 Shippable downstream tasks should use artifacts from build-mac-notarization. 601 602 release-eme-free-repack-mac-notarization 603 ---------------------------------------- 604 605 Mac notarization on signingscript (linux) using rcodesign. 606 607 Only available in production environments, as Apple doesn't offer a test 608 endpoint for notarizing apps. 609 610 Downstream tasks switch to build-mac-signing in non-shippable builds or level 1 611 environments. 612 613 repackage 614 --------- 615 Repackage tasks take a signed output and package them up into something suitable 616 for shipping to our users. For example, on OSX we return a tarball as the signed output 617 and this task would package that up as an Apple Disk Image (.dmg) 618 619 repackage-l10n 620 -------------- 621 Repackage-L10n is a ```Repackage``` task split up to be suitable for use after l10n repacks. 622 623 repackage-deb 624 ---------------- 625 These repackage tasks take signed Firefox Linux binaries and puts them in Debian packages. 626 627 repackage-deb-l10n 628 ------------------ 629 These repackage tasks take the signed langpacks (.xpi) binaries and puts them in Debian packages. 630 631 repackage-rpm 632 ---------------- 633 These repackage tasks take signed Firefox Linux binaries and puts them in RPM packages. 634 635 repackage-flatpak 636 ----------------- 637 These repackage tasks take signed Firefox Linux binaries and langpacks, and builds a flatpak. 638 639 repackage-signing 640 ----------------- 641 Repackage-signing take the repackaged installers (windows) and signs them. 642 643 repackage-signing-l10n 644 ---------------------- 645 Repackage-signing-l10n take the repackaged installers (windows) and signs them for localized versions. 646 647 mar-signing 648 ----------- 649 Mar-signing takes the complete update MARs and signs them. 650 651 mar-signing-l10n 652 ---------------- 653 Mar-signing-l10n takes the complete update MARs and signs them for localized versions. 654 655 mar-signing-autograph-stage 656 --------------------------- 657 These tasks are only to test autograph-stage, when the autograph team asks for their staging environment to be tested. 658 659 repackage-msi 660 ------------- 661 Repackage-msi takes the signed full installer and produces an msi installer (that wraps the full installer) 662 Using the ```./mach repackage``` command 663 664 repackage-signing-msi 665 --------------------- 666 Repackage-signing-msi takes the repackaged msi installers and signs them. 667 668 repackage-msix 669 -------------- 670 Repackage-msix takes a (possibly unsigned) package and produces a Windows MSIX package containing no langpacks using the 671 ```./mach repackage``` command. 672 673 These tasks are supposed intended for rapid iteration in ```try```. 674 675 repackage-shippable-l10n-msix 676 ----------------------------- 677 Repackage-msix takes a signed package and a list of signed langpacks and produces a Windows MSIX package using the 678 ```./mach repackage``` command. 679 680 The signed langpacks are produced on Linux, since langpacks are platform agnostic. 681 682 These tasks are for releases; they are complete, and therefore slower, and not intended for rapid iteration in 683 ```try```. 684 685 repackage-signing-msix 686 ---------------------- 687 Repackage-signing-msix takes Windows MSIX packages produced in ```repackage-msix``` and signs them. 688 689 repackage-signing-shippable-l10n-msix 690 ------------------------------------- 691 Repackage-signing-shippable-l10n-msix takes Windows MSIX packages produced in 692 ```repackage-signing-shippable-l10n-msix``` and signs them. 693 694 repackage-snap 695 -------------- 696 Repackage current packaged build as a Snap package 697 698 release-msix-push 699 -------------------- 700 Pushes msix repackage to the Microsoft Store. 701 702 repo-update 703 ----------- 704 Repo-Update tasks are tasks that perform some action on the project repo itself, 705 in order to update its state in some way. 706 707 partials 708 -------- 709 Partials takes the complete.mar files produced in previous tasks and generates partial 710 updates between previous nightly releases and the new one. Requires a release_history 711 in the parameters. See ``mach release-history`` if doing this manually. 712 713 partials-zucchini 714 ----------------- 715 Partials-zucchini takes the complete.mar files produced in previous tasks and generates partial 716 updates between previous nightly releases and the new one. Requires a release_history 717 in the parameters. See ``mach release-history`` if doing this manually. 718 The zucchini tool is compiled via toolchain task. The source code can be found at: 719 https://chromium.googlesource.com/chromium/src/components/zucchini/ 720 721 partials-signing 722 ---------------- 723 Partials-signing takes the partial updates produced in Partials and signs them. 724 725 post-balrog-dummy 726 ----------------- 727 Dummy tasks to consolidate balrog dependencies to avoid taskcluster limits on number of dependencies per task. 728 729 post-beetmover-dummy 730 -------------------- 731 Dummy tasks to consolidate beetmover dependencies to avoid taskcluster limits on number of dependencies per task. 732 733 post-beetmover-checksums-dummy 734 ------------------------------ 735 Dummy tasks to consolidate beetmover-checksums dependencies to avoid taskcluster limits on number of dependencies per task. 736 737 post-beetmover-components-dummy 738 ------------------------------- 739 Dummy tasks to consolidate beetmover-components dependencies to avoid taskcluster limits on number of dependencies per task. 740 741 post-langpack-dummy 742 ------------------- 743 Dummy tasks to consolidate language pack beetmover dependencies to avoid taskcluster limits on number of dependencies per task. 744 745 post-update-verify-dummy 746 ------------------------ 747 Dummy tasks to consolidate update verify dependencies to avoid taskcluster limits on number of dependencies per task. 748 749 fetch 750 ----- 751 Tasks that obtain something from a remote service and re-expose it as a 752 task artifact. These tasks are used to effectively cache and re-host 753 remote content so it is reliably and deterministically available. 754 755 packages 756 -------- 757 Tasks used to build packages for use in docker images. 758 759 diffoscope 760 ---------- 761 Tasks used to compare pairs of Firefox builds using https://diffoscope.org/. 762 As of writing, this is mainly meant to be used in try builds, by editing 763 taskcluster/kinds/diffoscope/kind.yml for your needs. 764 765 addon 766 ----- 767 Tasks used to build/package add-ons. 768 769 openh264-plugin 770 --------------- 771 Tasks used to build the openh264 plugin. 772 773 openh264-signing 774 ---------------- 775 Signing for the openh264 plugin. 776 777 webrender 778 --------- 779 Tasks used to do testing of WebRender standalone (without gecko). The 780 WebRender code lives in gfx/wr and has its own testing infrastructure. 781 782 instrumented-build 783 ------------------ 784 Tasks that generate builds with PGO instrumentation enabled. This is an 785 intermediate build that can be used to generate profiling information for a 786 final PGO build. This is the 1st stage of the full 3-step PGO process. 787 788 generate-profile 789 ---------------- 790 Tasks that take a build configured for PGO and run the binary against a sample 791 set to generate profile data. This is the 2nd stage of the full 3-step PGO 792 process. 793 794 geckodriver-signing 795 ------------------- 796 Signing for geckodriver binary. 797 798 geckodriver-mac-notarization 799 ---------------------------- 800 Apple notarization for mac geckodriver binary. 801 802 maybe-release 803 ------------- 804 A shipitscript task that does the following: 805 806 1. Checks if automated releases are disabled 807 2. Checks if the changes between the current revision and the previous releases 808 revision are considered "worthwhile" for a new release. 809 3. Triggers the release via ship-it, which will then create an action task. 810 811 l10n-bump 812 --------- 813 Cron-driven tasks that bump l10n-changesets files in-tree, using data from the l10n dashboard. 814 815 merge-automation 816 ---------------- 817 Hook-driven tasks that automate "Merge Day" tasks during the release cycle. 818 819 sentry 820 ------ 821 Interact with Sentry, such as by publishing new project releases. 822 823 system-symbols 824 -------------- 825 Generate missing macOS and windows system symbols from crash reports. 826 827 system-symbols-upload 828 --------------------- 829 Upload macOS and windows system symbols to tecken. 830 831 system-symbols-reprocess 832 ------------------------ 833 Call Crash-Stats API to reprocess after symbols upload. 834 835 scriptworker-canary 836 ------------------- 837 Push tasks to try to test new scriptworker deployments. 838 839 updatebot 840 ------------------ 841 Check for updates to (supported) third party libraries, and manage their lifecycle. 842 843 fuzzing 844 ------- 845 846 Performs fuzzing smoke tests 847 848 startup-test 849 ------------ 850 851 Runs Firefox for a short period of time to see if it crashes 852 853 attribution 854 ----------- 855 Injects attribution information into en-US installers. 856 857 attribution-l10n 858 ---------------- 859 Injects attribution information into localized installers. 860 861 snap-upstream-build 862 ------------------- 863 Perform a Firefox Snap build using upstream tooling 864 865 snap-upstream-test 866 ------------------- 867 Test a Firefox Snap built using upstream tooling 868 869 trigger-comm-central 870 -------------------- 871 Trigger a CI decision task on comm-central when conditions are met. Currently 872 used for verifying third party Rust code is consistent. 873 874 build-components 875 ---------------- 876 Build android-components. 877 878 build-bundle 879 ------------ 880 Build Focus, Klar, and Fenix android app bundles. 881 882 build-apk 883 --------- 884 Build Focus, Klar, and Fenix apks. 885 886 build-samples-browser 887 --------------------- 888 Build android samples browser. 889 890 signing 891 ------- 892 Sign android-components. 893 894 signing-bundle 895 -------------- 896 Sign Focus, Klar, and Fenix android app bundles. 897 898 signing-apk 899 ----------- 900 Sign Focus, Klar, and Fenix apks. 901 902 test-components 903 --------------- 904 Test android-components 905 906 test-apk 907 -------- 908 Test Focus, Klar, and Fenix apks. 909 910 ui-test-apk 911 ----------- 912 User interface tests for Focus, Klar, and Fenix apks. 913 914 android-browsertime 915 ------------------- 916 Browsertime tests for android. 917 918 android-startup-test 919 -------------------- 920 Startup test for android. 921 922 post-signing-dummy 923 ------------------ 924 Gating kind to wait for all android signing tasks. 925 926 beetmover-components 927 -------------------- 928 A beetmover task for android components. 929 930 beetmover-android-app 931 --------------------- 932 A beetmover task for android APKs and AABs. 933 934 push-apks 935 ----------- 936 Push Focus and Fenix APKs to the Samsung Galaxy Store. 937 938 push-bundle 939 ----------- 940 Push Focus and Fenix AABs to Google Play. 941 942 android-l10n 943 ------------ 944 Update android string resources from android-l10n repo. 945 946 release-update-product-channel-version 947 -------------------------------------- 948 Update the product channel version in Ship-It. 949 950 instrumented-build-apk 951 ----------------------- 952 Generate instrumented apks used to generate Baseline Profile for Android apps. 953 954 generate-baseline-profile-firebase 955 ---------------------------------- 956 Run baseline profile generation for Android on Firebase TestLab. 957 958 update-test 959 ----------- 960 Run tests to see if the Firefox executable can be updated to the latest release. 961 962 run-macrobenchmark-firebase 963 --------------------------- 964 Run Macrobenchmark for Android on Firebase TestLab. 965 966 instrumented-build-macrobenchmark-apk 967 ------------------------------------- 968 Generate instrumented apks used to run Macrobenchmark for Android apps.