Pipeline Execution 15.7 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-11-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 - Uploaded October 20, 2022
- Group Kickoff - Uploaded November 8, 2022
Theme: Secure CI_JOB_TOKEN by default
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
- Make the secure CI_JOB_TOKEN the default / usable for inbound
- Biggest Table Partitioned - ~"Category:Continuous Integration Scaling"
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 VerifyP1 issues that carryover from the previous milestone. -
Confidential issue - https://gitlab.com/gitlab-org/gitlab/-/issues/375365 -
Confidential issue - https://gitlab.com/gitlab-org/gitlab/-/issues/373778 -
FRONTEND - new interface for inbound CI_JOB_TOKEN (gitlab-org/gitlab#375782 - closed) -
Enable inbound job token scope by default for n... (gitlab-org/gitlab#340822 - closed) -
Pipeline step log entries have too many fields (gitlab-org/gitlab#371636 - closed) -
[Data Integrity Issue] `Ci::RetryBuildService` ... (gitlab-org/gitlab#340998 - closed)
VerifyP2
None.
VerifyP3
-
Backend: git push option `merge_request.merge_w... (gitlab-org/gitlab#336542 - closed) -
Ensure after_script is called for timed out pip... (gitlab-org/gitlab#15603)
~"type::bugs" of note
-
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
As part of cross functional prioritization framework we track the % of issue types and weights in planning to forecast against the team's current needs.
Issue Type | Issues | Weight | Percentages issues/weight |
---|---|---|---|
typefeature | n | n | x% / y% |
typebug | n | n | x% / y% |
typemaintenance | n | n | x% / y% |
Other | n | Note about what these are |
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