Pipeline Execution 15.5 Planning Issue
What's the focus, where can I find issue candidates for the milestone?
Issue Boards
PE workflow board | Issues by Team Member
This issue is closed as of 2022-09-17
The Single Source of Truth (SSOT) for the status of issues in the milestone is the milestone board where issues are stack ranked by priority.
🎥
Recordings - Refinement Kickoff - Published 2022-08-26
- Group Kickoff - Published 2022-09-14
Theme: The next step in secure pipelines
Goals for the milestone
- Meet Reliability issue SLOs - VerifyP1 issues -> Ensuring we have a reliable and stable platform maps to the GitLab Hosted First investment theme
- Ship the next iteration of CI_JOB_TOKEN -> maps to the investment theme of Extending our Lead in CI/CD by providing more secure ways to let pipelines run.
- Set cost factor to 1 for all public projects to complete big deliverables of ~"CI minutes" epic -> making it easier to understand CI/CD Minute consumption (and having predictable costs) maps to the Extend our lead in CI/CD Investment Theme
-
Complete the last step of Backend: Harden CI limit for public projects (gitlab-org/gitlab#337245 - closed) by setting cost factor for public projects to 1.
-
- Reduce carryover of Deliverable issues from %15.4 by half. -> Doesn't map to an investment theme but ensures we can have a good idea what we can deliver each milestone and stay nimble to adjust to changing priorities without carrying over large amounts of half done work each milestone.
Issues of note
This is a breakdown of the issues in the milestone. For more information about how we prioritize check out the handbook page.
VerifyP1
- Any issues carried over from previous milestone
-
Backend: Enable a ci_token permission flow for ... (gitlab-org/gitlab#346298 - closed) -
Adjust/lower arbitrary limits from data observa... (gitlab-org/gitlab#358975 - closed) -
Backend: Add additional logging in Kibana for t... (gitlab-org/gitlab#356570 - closed) -
Confidential issue gitlab-org/gitlab#365532 (closed)
VerifyP2 issues
-
Spike: Research: CI/CD fair scheduling algorith... (gitlab-org/gitlab#354343) -
Backend: Scheduled pipelines are triggering mul... (gitlab-org/gitlab#338609 - closed) -
Backend: Harden CI limit for public projects (gitlab-org/gitlab#337245 - closed)
Infradev Issues
-
Add issue here - link -
Add issue here - link
Feature flags to be rolled out this milestone
-
Add issue here - link -
Add issue here - link
Quality tests/Flaky tests to be resolved
-
Add issue here - link -
Add issue here - link
Docs improvement
-
Add issue here - link -
Add issue here - link
Issue Breakdown
Issue Type | Issues | Weight | Percentages issues/weight |
---|---|---|---|
~"type::feature" | 4 | 0 | x% / x% |
~"type::bug" | 0 | 0 | x% / x% |
~"type::maintenance" | 2 | 0 | x% / x% |
Other | 1 | This is a planning/team work issues. |
Designer/UX
- Epic: gitlab-org&5866
Planning Tasks
-
PM highlights work for Deliverables, User Experience, Bug Fixes, Security Fixes, Technical Debt sections -
PM describes how this milestone aligns with the company's OKRs -
EMs assign issues with ~needs weight
label in~workflow::planning breakdown
to engineers for review ahead of the milestone kickoff. -
By the 15th - EM applies ~deliverable
and~stretch
labels to issues. -
Engineers begin working on issues in workflow::ready for development
Edited by James Heimbuck