Pipeline Execution 15.10 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

This issue is closed as of 2023-02-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 🎥

Milestone Theme: Make it obvious if an MR can be merged.

Goals for the milestone

  1. Meet Reliability issue SLOs - VerifyP1 issues
  2. Add CI_JOB_TOKEN events to audit logs -> Mapping to the FY24 investment theme of Advanced Security and Compliance.
  3. Backend: Make it easier to understand and diffe... (gitlab-org/gitlab#217718 - closed) -> Support a world-class DevSecOps experience by reducing complexity of why that pipeline ran.
  4. Replace merge strategy labels with `Auto-merge`... (gitlab-org/gitlab#359057 - closed) -> Support a world-class DevSecOps experience by reducing complexity of if/when the Merge Request can merge.

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

  1. gitlab-org/gitlab#350617 (closed)
  2. Add issue here - link

Infradev Issues

  1. Add issue here - link
  2. Add issue here - link

VerifyP2

  1. Add audit logging for secure CI_JOB_TOKEN setting (gitlab-org/gitlab#338255 - closed)
  2. Create Columns for standard and OSS cost factor... (gitlab-org/gitlab#363215 - closed)
  3. Backend: Store Gitlab Contribution Namespaces i... (gitlab-org/gitlab#367575 - closed)
  4. Spike: Research: CI/CD fair scheduling algorith... (gitlab-org/gitlab#354343)

VerifyP3

  1. Backend: Make it easier to understand and diffe... (gitlab-org/gitlab#217718 - closed)
  2. Shared definition for ci cd limit descriptions (gitlab-org/gitlab#362162 - closed)

typebug of note

  1. Lazy Load Manual Builds to avoid Request Timeouts (gitlab-org/gitlab#207994 - closed)
  2. Backend: Query cancelled due to statement timeo... (gitlab-org/gitlab#328596 - closed)
  3. Backend: Interruptible pipelines are not cancel... (gitlab-org/gitlab#287780 - closed)
  4. Merge train possible despite blocked merge (gitlab-org/gitlab#383137 - closed)
  5. Backend: Rebasing MR as Maintainer leaks parent... (gitlab-org/gitlab#359955 - closed)
  6. CI/CD minutes usage doesn't show up for January... (gitlab-org/gitlab#388717 - closed)
  7. CI Jobs page has error fetching the jobs for pr... (gitlab-org/gitlab#389347 - closed)

Feature flags to be rolled out this milestone

  1. Add issue here - link
  2. Add issue here - link

Quality tests/Flaky tests to be resolved

@richard.chong are there specific flaky tests you want to take on in this milestone and/or need developer support for?

  1. Add issue here - link
  2. Add issue here - link

Docs improvement

@drcatherinepope @marcel.amirault I don't see any docs-only issues in the milestone. Are there things you want to line up here based on other planned work?

  1. Add issue here - link
  2. Add issue here - link

Issue Breakdown/Cross Functional Planning

See discussion here.

Designer/UX

  1. 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 Caroline Simpson