Scheduling issue for the 15.[345]
Product Outlook
Improve distribution team pipelines to increase velocity and developer productivity
In the similar theme of our build efficiency, there are improvements to our pipelines that we can make to ensure our team can mitigate unscheduled work due to the complexity of our pipelines. Distribution pipelines, such as those building Omnibus and Cloud Native, grew organically and iteratively as problems were solved. Tight product deadlines and demands have prevented the team from slotting in work to improve the pipelines and take the necessary steps to increase efficiency.
A reduction in unplanned work not only decreases overall workload but, it also allows team members to keep focus on issues and projects without frequent distraction.
Issues from 15.5 Kick-off video
- Add Packages for AL2022
- Support multiple architecture build for CNG images
- Spike: Viability of CNG Support for multi-arch images
- Add a logrotate to limit ephemeral storage consumption
- Investigate and document workaround for mirroring gitlab rpm repos via Red Hat satellite
- Add kas container to dsop-scripts
Issues from 15.4 Kick-off Video
- Add Packages for Ubuntu 22.04
- Support Backups with Azure Blob Storage
- Encrypt incoming_email_password in the rails codebase
- Encrypt non-rails passwords stored in
gitlab.rb - Document near zero downtime PostgreSQL major upgrade for Patroni Cluster
- Upgrade badge seems to be gone from Admin view
Bugs
In 15.4 we are committing to continuing triage high priority issues on our new bug dashboard.
Distribution Build and Deploy are still working on high priority cross-functional tasks including a Rapid Action for compliance upgrades, Operator work and other projects. We will continue to schedule bugs as we have, and work on burning them down in a few milestones.
Deliverable Board
Issues on this board have already been reviewed and scheduled for the upcoming release. Each column represents a priority level. The highest ranked issues for each priority level are at the top of each column.
For Scheduling board
Used with continuous scheduling process to provide potential candidates, but before assigning a deliverable milestone. Board includes groupdistribution For Scheduling issues across gitlab-org projects.
Maintenance (formerly Tech Debt) board
Prioritized maintenance issues should be scheduled each release to prevent it from growing unchecked. Board includes groupdistribution typemaintenance issues across gitlab-org projects.
Sub-Team Boards
Shows issues broken out by ~"Distribution:Deploy" and ~"Distribution:Build" team labels, to ensure we don't have groupdistribution labels missing their sub-team.
Ongoing Epics
Some epics are used to collect a common series of issues that we are slowly working through release-over-release. This means we typically try to ensure one task from the epic is in each milestone. We are currently marking these with the workflowscheduling label.
Comments
The team is encouraged to add potential candidates and contextual comments to this issue. These are reviewed weekly with PM, EM and Staff engineers to determine impact and priority.