Pipeline Execution 15.2 Planning issue

changed milestone to %15.2

assigned to @jheimbuck_gl, @marknuzzo, @samdbeckham, @v_mishra, and @richard.chong

changed the description

marked the checklist item Investigate fixes for slow loading of pipelines... (gitlab-org/gitlab#341462 - closed) as completed

marked the checklist item Frontend: Show year in CI minutes usage graph (gitlab-org/gitlab#335968 - closed) as completed

marked the checklist item Remove ignored_components from PE error budget (gitlab-org/gitlab#348552 - closed) as completed

changed the description

@jheimbuck_gl I've highlighted some changes we may need to make in the planning:

gitlab-org/gitlab#346400 (comment 965685364)
Instead of gitlab-org/gitlab#352420 we now broke down the issue into 4 and the first iteration is gitlab-org/gitlab#363215 (closed)

/cc @marknuzzo

Thanks @fabiopitino for this note.

It seems that gitlab-org/gitlab#352420 is now more of the epic to track the overall work and if so, moving gitlab-org/gitlab#363215 (closed) into VerifyP2 would make sense and we can convert gitlab-org/gitlab#352420 to an epic. @jheimbuck_gl WDYT?

@marknuzzo I think we left gitlab-org/gitlab#352420 with work in it so we'd need to replace it after promoting it. I'm fine either way if that's how it is best to track those. Just having the issues is fine too.

We can leave as-is then since the issues are linked in the order of the work to be done. Thanks @jheimbuck_gl

@marknuzzo @fabiopitino - I think the blocking on these is out of order, i see the issue in 15.2 is blocked by the issue in 15.3 which is blocked by the one in 15.4. Will one of you take on getting those into the proper order please?

@jheimbuck_gl I've fixed the blocked by relations across all these issues.

changed the description

mentioned in issue gitlab-com/Product#4291 (closed)

changed the description

@jreporter - ping for you on the team's 15.2 planning issue. We're taking a hard look at the backend only issues and will be removing more of those as well as blocked issues to clear some room. We're going to need to account for the hackathon week happening at the beginning of this milestone as well in those reductions.

Thanks @jheimbuck_gl @marknuzzo - what is the average issues closed and weight the team delivers in a milestone? In looking at all of the issues scheduled for 15.2 it still seems overly ambitious.

36 issues: https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=created_asc&state=opened&label_name%5B%5D=group%3A%3Apipeline%20execution&milestone_title=15.2&first_page_size=20

19 of these issues are not in workflowready for development

@jreporter L5 after 15.0 was 37 issues / 30 weight. We expect we'll need to be 25% below that for %15.2 to account for the Verify Week hackathon. I'm working to get that list of 36 down to 10 today to account for these two things and have a realistic amount of work in the milestone.

cc @samdbeckham for awareness / planning assistance.

Super thanks @jheimbuck_gl - I would strongly consider the weight and workflow status drive those priority issues

@marknuzzo @samdbeckham @richard.chong - I took a pass at slimming down the 15.2 milestone. Where I need some help is further slimming down the list of 13 typemaintenance issues.

It looks like 4 of those are currently blocked 3 by the same issue which you're assigned to @richard.chong - do you anticipate getting the blocker done in 15.1 and if so all 3 of these issues done in 15.2?
3 of the issues are CI Scaling which I'm assuming Grzegorz and Marius have capacity for.
If you'd review the rest of those this week to help us slim our 15.2 plan down further it'd be appreciated!

@jheimbuck_gl Yes, the MR actually is already approved but merging is just blocked by something that is unrelated to my changes. Once it's merged, all of these are then unblocked and ready to be worked on. They're introducing simple tests so it should be doable within %15.2.

@richard.chong - thanks! With the 2 Quality issues in %15.1 we could have up to 6 in %15.2 I think we should prioritize the 3 most important for now and schedule the rest for later. what do you think?

@jheimbuck_gl Sounds good to me. There were 3 that I moved off of %15.1 that I wanted to get to in %15.2 as part of my QE OKR this quarter.

I may end up pulling 1 more in before the end of this milestone but I'll leave it in %15.2 for now since things did get delayed for a bit with some work getting blocked recently.

changed the description

mentioned in issue gitlab-com/www-gitlab-com#13538 (closed)

mentioned in issue gitlab-com/Product#4321 (closed)

changed the description

Thread for Deliverable and Stretch issues for %15.2

@marknuzzo @samdbeckham @v_mishra @richard.chong

Carryover from 15.1

Deliverable issues

It looks like all Deliverables will be delivered.

Stretch issues

Include the list of tags for each job in Extern... (gitlab-org/gitlab#335904 - closed) was picked up as a Community contribution, I would not mark it Deliverable
Backend: Add cached denormalized count of jobs ... (gitlab-org/gitlab#360672 - closed) We should promote this to Deliverable it is blocking rollout of the new jobs_table_vue and search functionality for jobs.

Top priorities in 15.2 - Deliverable candidates

VerifyP1 issues
- 5 issues, a mix of corrective action and security and prioritizing reduced cost factor for forks of public projects given the friction for contributors to GitLab other OSS projects are probably feeling the same with contributors running out of minutes.
VerifyP2 issues
- 2 issues, one is a blocker for further work on new cost factor columns that enable changing the cost factor in the UI.
Issues blocking other work
- Backend: Make `ci_pipeline_size` and `ci_active... (gitlab-org/gitlab#212365 - closed)

Secondary priorities in 15.2 - Stretch candidates

VerifyP3 issues
- Backend: Ensure no pipeline runs when rebasing ... (gitlab-org/gitlab#349362 - closed) - this isn't technically blocking the frontend work and is itself blocked but should be able to be shipped in the milestone.
Other typebug issues
- 2 more issues

Total Deliverable issue list would be 9 with the promoted stretch issue from %15.1 which is a pretty big increase over the 6 Deliverables the team had in 15.0 and 15.1.

Total Stretch issue list would be 4 issues if the Stretch label is left on the Community contribution from %15.1

@marknuzzo @samdbeckham - adding an agenda item to our 1:1:1 tomorrow for this and I will apply the labels as described here after after that discussion and/or comments here. Thanks!

@marknuzzo @samdbeckham I think I missed adding the agenda item

I'm applying labels anyway! YOLO!!!! ;)

Here's a summary of what i've done/will do

Applied Deliverable to all VerifyP1 issues
Apply Deliverable to 2 VerifyP2 issues, reduce cost factor for GitLab contributions and the issue for adding columns for cost factor to the database.
Apply Stretch to the VerifyP3 issue and 2 bugs.

I'll also update the label on Backend: Add cached denormalized count of jobs ... (gitlab-org/gitlab#360672 - closed) to Deliverable if it does not finish up in %15.1

Hi @gitlab-com/pipeline-execution-group -

As a friendly reminder as it relates to %15.2 planning, please keep in mind that we have our Verify Hackathon week during the upcoming milestone so please factor that into your workload.

changed the description

mentioned in issue gitlab-org/gitlab#352830 (closed)

mentioned in issue gitlab-com/Product#4356 (closed)

changed the description

marked the checklist item PM highlights work for Deliverables, User Experience, Bug Fixes, Security Fixes, Technical Debt sections as completed

marked the checklist item PM describes how this milestone aligns with the company's OKRs as completed

marked the checklist item EMs assign issues with ~needs weight label in ~workflow::planning breakdown to engineers for review ahead of the milestone kickoff. as completed

changed the description

mentioned in issue gitlab-org/technical-writing#627

@jheimbuck_gl I went through the listed issues and added documentation to any that I expect will need docs updates as part of the work (it was only 1-2, everything else was good already).

Also, FYI, the TW team is at reduced capacity for this milestone: gitlab-org/technical-writing#627

I'm not going to be OOO, but others will be out so those of us that are around will be covering extra groups for a while, so there might be delays on non-critical work.

cc @marknuzzo @samdbeckham @v_mishra

Thanks for letting us know @marcel.amirault

The whole stage will be slightly reduced capacity this month due to PTO and the verify team week

thanks for the review and heads up @marcel.amirault - I don't think we'll have any release post items this milestone so that should help with load ;)

changed the description

closed

marked the checklist item By the 15th - EM applies ~deliverable and ~stretch labels to issues. as completed

marked the checklist item Engineers begin working on issues in workflow::ready for development as completed

marked the checklist item Backend: Ensure no pipeline runs when rebasing ... (gitlab-org/gitlab#349362 - closed) as completed

Issue Type	Issues	Weight	Percentages issues/weight
~"type::feature"	4	3	19% / 11%
~"type::bug"	6	10	28% / 35%
~"type::maintenance"	11	15	53% / 54%
Other	1	This is a planning/team work issues.

Pipeline Execution 15.2 Planning issue

This issue is closed as of 2022-06-17

Recordings

Goals for the milestone

VerifyP1

Infradev Issues

VerifyP2

VerifyP3

Feature flag

Quality tests

Docs improvement

Issue Breakdown

Designer/UX

Planning Tasks

Designs

Child items ...

Activity

Thread for Deliverable and Stretch issues for %15.2

Carryover from 15.1

Top priorities in 15.2 - Deliverable candidates

Secondary priorities in 15.2 - Stretch candidates