GitLab Pipeline Execution, 21 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Pipeline Execution 15.1 Refinement/Planning Kickoff

Description

This video walks through the theme and goals for the 15.1 milestone that the Pipeline Execution team will be working towards.

The issue itself can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/98

The needs weight board can be found here: https://gitlab.com/groups/gitlab-org/-/boards/4178322?label_name[]=group%3A%3Apipeline%20execution&label_name[]=needs%20weight&milestone_title=15.1

A

Izzy, uh this is jade's product manager for the pipeline execution group, and I am sharing my screen on our 15.1 planning issue. uh So this is kicking off our refinement on the 15-1 milestone.

A

1 will be kicking off in may and shipping in june. uh So, looking at our theme, as we think about themes for our milestones, um we're going to be enforcing public uh or enforcing the ci limits on all public projects with the 15-1 milestone and that'll actually happen really early in the milestone. um The work there is happening in 15.

A

Oh, the feature flight will be flipped on june 1st to go along with that, though, we have a secondary theme of using that reduced cost cost factor for public forks, so the contributors to public projects that aren't in the open source project, yet our open source program yet can do so at the reduced rate and not at that 1.0 cost factor.

A

Our main theme, though, really for the milestone- and this is going to be a continuing theme for the next couple milestones- is ensuring that we're meeting our reliability issue as slos and so all of those are listed in the verify p1 column or they have a verify p1 label, and that is all that is in that column, as you can see here under that categorization with a few confidential issues which I'm not going to click into and then a creating a test- and this is a follow-up corrective action from an incident that we had um so really.

A

The theme um for enforcing the ci and reduced cost factor. All of that kind of falls into verify. P2, that's we're putting more directional and product priorities and then verify p3 is a bit of a continuation there, but also things that are bugs that are missed, slo and trying to knock down that list of missed slo high priority high severity bucks.

A

um So as you're looking at verify, p1 p3, that's how you can think about that I've merged together, where we've called out front, end work before and issues that only have a front end label have that label here in the list. So you can take a look at those and those are easy to move on for our front end team, and we do have a couple of feature flags that we're flipping during a milestone that ci minutes cost factor is one of them.

A

um So those are the big themes and the couple of goals that we have for fifteen one. uh If you're looking at the planning breakdown column on the board, which I will link to or on our new needs weights board, um all of those are in stack rank order, verify p1, p2, p3 and then the rest uh they're all ranked there in both of those boards, and it does look like those match up. I'm hiding confidential issues here just so, I can make this video public and share it.

A

uh So thanks so much if you have any questions, comment on the video or send me a dm, much more likely to get a response that way thanks.