Pipeline Execution 15.8 Planning issue
What's the focus, where can I find issue candidates for the milestone?
Issue Boards
PE workflow board | Issues by Team Member
🎥
Recordings - Refinement Kickoff - Published November 29, 2022
- Group Kickoff - Published December 15, 2022
This issue is closed as of 2022-12-19
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.
Theme: Security and Reliability
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 inbound project workflow of CI_JOB_TOKEN the default for new projects
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 - gitlab-org/gitlab#290955 (closed) -
Confidential issue - https://gitlab.com/gitlab-org/gitlab/-/issues/372736 -
Enable inbound job token scope by default for n... (gitlab-org/gitlab#340822 - closed) -
SPIKE: review after_script POC (gitlab-org/gitlab#361502 - closed) -
Backend: Recalculate remaining minutes on Addit... (gitlab-org/gitlab#350617)
VerifyP2
-
Move CreateDeployments out of the pipeline crea... (gitlab-org/gitlab#383600 - closed) -
Spike: Research: CI/CD fair scheduling algorith... (gitlab-org/gitlab#354343)
Feature flags to be rolled out this milestone
-
[Feature flag] Rollout of `ci_build_partition_i... (gitlab-org/gitlab#385401 - closed) -
Add issue here - link
Quality tests/Flaky tests to be resolved
-
Add issue here - link
Docs improvement
-
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.
This planning happens in a comment thread of this issue.
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