Release Engineering
For bugs related to all aspects of Mozilla's Release Engineering pipeline, including branded releases, continuous automation, release automation, tools, repos and hooks, machine issues, loaner machines, buildbot.
Select a component to see open bugs in that component:
Applications: Mapper
Issues related to the Mapper REST API tool
Applications: MozharnessCore
Issues related to mozharness's core, Mozilla's configuration-driven script harness should be filed here.
Applications: Shipit (backend)
Issues related to the core, business logic and REST API of our release dashboard (Ship-it).
Applications: Shipit (frontend)
Issues related to the web admin interface of our release dashboard (Ship-it).
Applications: ToolTool
Issues related to the core functionality of our client program that manipulates the generic binary artifacts (Tooltool).
Applications: TreeStatus
Issues related to the core and business logic of our tool (TreeStatus) to toggle open/closed state of gecko-related development trees.
Custom Release Requests
Issues related to custom builds of Firefox produced by Mozilla, or updates to those builds
Documentation
Any documentation related item
Firefox-CI Administration
Requests for changes in services that affect Firefox-CI.
General
This component is used for goals, tracking bugs, and any general RelEng work that spans across different RelEng components. Anything that doesn't fit in any other component goes here.
Release Automation: Bouncer
Issues related to bouncer communication to serve releases
Release Automation: Flatpak
Issues related to packaging and delivering Firefox in Flathub's flatpaks
Release Automation: L10N
Issues related to localization within the release workflow
Release Automation: Other
Anything that doesn't fit in any of the sibling components
Release Automation: Pushapk
Issues related to transferring mobile APKs to various cloud stores
Release Automation: Signing
Issues related to signing within the release workflow
Release Automation: Snap
Issues related to packaging and delivering Firefox in Ubuntu's a
Release Automation: Updates
Issues related to generation, submission and serving of updates (balrogworkers, tools, etc)
Release Automation: Uploading
Issues related to transferring artifacts from one place to another (beetmoverworkers)
Release Requests
Issues related to custom builds of Firefox produced by Mozilla, or updates to those builds
Tools
This component tracks large scale tools used to interact with RelEng systems. Some examples include (but are not limited to): * vcs2vcs, balrog, tryserver/trychooser, cloud-tools, buildapi, self-serve, hg/git mapper, integration-with-s3, tools-for-sheriffs, autoland, kittenherder... * alerts for colo outages, long-running-jobs, * reports for wait-times, try-server-top-users, cost reporting, slave health, ...