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:
Issues related to the core, business logic, and REST API of our update server (Balrog)
Issues related to the web admin interface of our update server (Balrog).
Issues related to mozharness's core, Mozilla's configuration-driven script harness should be filed here.
Issues related to the Services's core, RelEng's centrepoint to source, maintain and deploy various applications.
Issues related to the core, business logic and REST API of our release dashboard (Ship-it).
Issues related to the web admin interface of our release dashboard (Ship-it).
Issues related to the core functionality of our client program that manipulates the generic binary artifacts (Tooltool).
Issues related to the core and business logic of our tool (TreeStatus) to toggle open/closed state of gecko-related development trees.
Issues related to custom builds of Firefox produced by Mozilla, or updates to those builds
Any documentation related item
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.
Issues related to localization within the release workflow
Anything that doesn't fit in any of the sibling components
Issues related to transferring mobile APKs to various cloud stores
Issues related to signing within the release workflow
Issues related to packaging and delivering Firefox in Ubuntu's a
Issues related to generation, submission and serving of updates (balrogworkers, tools, etc)
Issues related to transferring artifacts from one place to another (beetmoverworkers)
Issues related to custom builds of Firefox produced by Mozilla, or updates to those builds
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, ...