Pipeline Execution 16.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
Current/Upcoming Security issues
🎥
Recordings - Refinement Kickoff - TBD
- Group Kickoff - TBD
Projected Capacity
Capacity for milestone and CI data partitioning issues
(Based on 100% = 7 BE, 2 FE at 100% capacity)
BE = 68% (eqv. 4.7 dev), FE = 100% (eqv. 2 dev)
Theme: Add the theme here
Goals for the milestone
- Delivery after_script cancellation status to reduce costs for our customers
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
-
Disallow Pipeline and Job Cancellation (Frontend) (gitlab-org/gitlab#410634 - closed) • Payton Burdette • 16.7 • On track frontend -
Add ability to show job log full screen (gitlab-org/gitlab#363617 - closed) • Jose Ivan Vargas • 16.7 frontend -
Add Merge immediately option without interrupti... (gitlab-org/gitlab#423922 - closed) • Jose Ivan Vargas • 16.7 frontend Category:Merge Trains -
Add new table to for unique job names (Part 1) (gitlab-org/gitlab#423904 - closed) • Max Fan • 16.11 Blocks Frontend backend -
Add new keyword to support running after_script... (gitlab-org/gitlab#398774 - closed) • Allison Browne • 16.8 • On track backend critical-customer-escalation -
Add canceling state for jobs (gitlab-org/gitlab#399215 - closed) • Allison Browne • 16.10 backend critical-customer-escalation -
Send Canceling status when pipeline cancel butt... (gitlab-org/gitlab#399296 - closed) • Allison Browne • 16.10 • On track backend critical-customer-escalation -
Add a cancel button for graceful shutdown of pi... (gitlab-org/gitlab#399294 - closed) • Jose Ivan Vargas • 16.8 frontend critical-customer-escalation
Stretch
-
Change the empty state for pipeline widget when... (gitlab-org/gitlab#425062 - closed) • Jose Ivan Vargas • 17.1 frontend -
Show MR link for branch based pipelines (gitlab-org/gitlab#416134 - closed) • Jose Ivan Vargas • 16.9 -
Add pipeline subscription queries - GraphQL (gitlab-org/gitlab#425284 - closed) • Jose Ivan Vargas • 16.7
CI Data Partitioning
-
Update queries to include partition_id filter f... (gitlab-org/gitlab#423054 - closed) • Marius Bobin, Max Orefice • 16.7 • Needs attention -
Investigate ci_builds <-> taggings relation in ... (gitlab-org/gitlab#382210 - closed) • Marius Bobin • 16.7 • Needs attention -
Define id trigger on p_ci_builds table (gitlab-org/gitlab#421173 - closed) • Marius Bobin • 16.7 • On track -
Switch current partition_id value to 101 for ci... (gitlab-org/gitlab#387810 - closed) • Marius Bobin, Max Orefice • 16.7 • At risk -
Ensure that all tables that reference ci_job_ar... (gitlab-org/gitlab#429903 - closed) • Panos Kanellidis • 16.7 • On track -
Ensure id uniqueness on p_ci_job_artifacts (gitlab-org/gitlab#429905 - closed) • Max Orefice • 16.10 • Needs attention -
Add index for partitioned PK on ci_job_artifacts (gitlab-org/gitlab#429002 - closed) • Max Orefice • 16.7 -
Ensure that all tables that reference ci_stages... (gitlab-org/gitlab#430720 - closed) • Panos Kanellidis • 16.7 • On track -
Ensure id uniqueness for p_ci_stages (gitlab-org/gitlab#429937 - closed) • Max Orefice • 16.10 • On track -
Add index for partitioned PK on ci_stages (gitlab-org/gitlab#429001 - closed) • Panos Kanellidis • 16.7 • Needs attention -
Ensure id uniqueness on `p_ci_pipeline_variables` (gitlab-org/gitlab#429939 - closed) • Max Orefice • 16.9 • On track -
Add index for partitioned PK on ci_pipeline_var... (gitlab-org/gitlab#429000 - closed) • Panos Kanellidis • 16.7
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 -
By 7th - DRI for milestone refinement assigns issues with ~needs weight
label in~workflow::planning breakdown
to engineers for review ahead of the milestone kickoff. -
By 11th - DRI for milestone refinement follows up with engineers about issues not in ~workflow::read for development
-
By 14th - EM assigns any unassigned issues in the milestone -
By 16th - The team has discussed potential ~Deliverable
and~Stretch
labels and have indicated commitment with a👍 or👎 in the planning issue. -
By 19th - EM reviews ~deliverable
and~stretch
labels to assigned to issues. -
By 19th - EM ensures all issus are assigned. -
EM / PM remove any remaining issues form ~workflow::planning breakdown
-
Engineers begin working on issues in workflow::ready for development
Reference for How We Plan
Edited by Caroline Simpson