Scheduling is for the 15.[678] release
Product Outlook
15.8
Add Multi Arch Support to Cloud Native GitLab
New architectures are available to build GitLab on such as AArch64 and arm64. We need to be compatible with these new systems and the future of ARM cpus. We need to support these new architectures as well as the ones we currently support and do so efficiently.
Improve Distribution Team Pipelines
The Distribution team is facing an increase in unscheduled work caused by complexity in the pipelines. Pipelines are not providing complete coverage based on how the team needs to test deliverables. This Epic is partially related to technical debt tasks to decrease this complexity and take advantage of newer GitLab CI features will help improve team velocity, and some new feature work.
Improve Contributor Experience in Distribution Projects
The Distribution team would like to improve how we enable contributors to collaborate on Distribution items. Distribution is a difficult area of GitLab which makes it difficult to know where to start when hoping to contribute to Distribution related item. We want to be able to work with the community more which would help deliver user requested issues more rapidly.
Secure Solution for managing Omnibus secrets
GitLab configuration files contain plain text passwords that are used to authenticate connections to other services required for GitLab operations. GitLab passwords are currently read from gitlab.yml. They are stored in both gitlab.yml and gitlab.rb. When Chef updates the YAML file the passwords are output to the log. This is not a secure way to handle passwords and often becomes a blocker or concern for customers that need GitLab to meet basic security requirements.
Issues in Kickoff Video
- CNG: Use builds for building and tagging Docker images
- Provision Kubernetes clusters for housing multi-architecture CNG build fleet
- Refactor Job names to not rely on .Release.Revision
- Make use of Releases feature
- Process for creating and updating package and repo signing keys
- Encrypt incoming_email_password in the rails codebase
15.7
Improve Distribution Team Pipelines
The Distribution team is facing an increase in unscheduled work caused by complexity in the pipelines. Pipelines are not providing complete coverage based on how the team needs to test deliverables. This Epic is partially related to technical debt tasks to decrease this complexity and take advantage of newer GitLab CI features will help improve team velocity, and some new feature work.
Secure Solution for managing Omnibus secrets
GitLab configuration files contain plain text passwords that are used to authenticate connections to other services required for GitLab operations. GitLab passwords are currently read from gitlab.yml. They are stored in both gitlab.yml and gitlab.rb. When Chef updates the YAML file the passwords are output to the log. This is not a secure way to handle passwords and often becomes a blocker or concern for customers that need GitLab to meet basic security requirements.
15.6
General Issue Backlog
The past few milestones the Distribution team has been involved with urgent cross-portfolio projects and compliance work, which has required us to push out a miscellaneous set of important issues. This milestone, 15.6, will serve as an opportunity to complete these important issues.
Secure Solution for managing Omnibus secrets
GitLab configuration files contain plain text passwords that are used to authenticate connections to other services required for GitLab operations. GitLab passwords are currently read from gitlab.yml. They are stored in both gitlab.yml and gitlab.rb. When Chef updates the YAML file the passwords are output to the log. This is not a secure way to handle passwords and often becomes a blocker or concern for customers that need GitLab to meet basic security requirements.
Issues from Kickoff videos
- Add Packages for AL2022
- Support multiple architecture build for CNG images
- Encrypt all Rails passwords stored in
gitlab.rb - Encrypt all non-Rails passwords stored in
gitlab.rb
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.