GitLab Pipeline Execution, 29 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Pipeline Execution 15.8 Refinement / Planning kickoff

Description

The 15.8 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/120

The needs weight board can be found here: https://gitlab.com/groups/gitlab-org/-/boards/4178322?not%5Bmilestone_title%5D=Started&label_name%5B%5D=group%3A%3Apipeline+execution&label_name%5B%5D=needs+weight

A

18 uh wanted to do a belated 15-8, refinement, kickoff I think we're already looking at the issues in the Milestone, which is great I, wanted to share the theme and the goals for the Milestone. So our theme around 15 8, which will be delivering in January, uh is security and reliability. Reliability continues to be a theme for us, as we continue to get verified p1s just ensuring that we're meeting our slos there to ensure we have a reliable and stable platform for gitlab.com um and then number two.

A

There is shipping some pagination for endpoints identified as a contributing factor to our error budget, overage that we're currently in. We think that that's been mitigated we're back in the green for the last seven and last 14 days as of today. Last time I looked, but we do want to get those cleaned up and so you'll find those in a confidential issue.

A

um And then it's just going to be a stretch for us to wrap up the CI minutes. Work, making it easier to understand the cicd minute consumption having predictable costs.

A

um That's cleaning up some of the things that we did as part of the CIA minute work um getting into the UI, uh some of the things to set new cost factors uh stuff like that cleaning up that Tech debt. So it's wrapping up some things that we pulled out of the Epic so that we could get the Epic closed.

A

So those are the big themes um and goals for the Milestone as they stand today um and then issues of note, we have a number of verified p1s right now we have five that are scheduled into the Milestone plus our carryover and looking at 15 7. Today it looks like we'd be carrying over 7 12, which is quite a few I know that three of those are in Dev.

A

uh One is blocked and a couple of children planning, uh but it is well as a team we're looking at those and working to get those moved over to the right, so we get them shipped and in 157, we've already closed three verified P months, which is great um and then verified, p2s uh doing some tracking around the ECI job token access, um adding some audit logging for that and then, ideally, we can get into some object model realignment for merge, merge, train category um that might end up being a stretch as well or drop out of the Milestone altogether, although it would definitely help move that category forward.

A

So as we think about our cross-functional breakdown, I started a thread a couple of days ago in this issue and I'll link to it when I drop the video into the slack Channel as well. um So things to consider, we have some open security issues. uh Four of those were in 15 7 3 were remaining and they're scheduled into 15 8. we've talked about or what our breakdown was in 1507, where we ended up was Vibe features, 12 bugs 15 maintenance issues.

A

I know that did include CI scaling work as well, um which we're starting to work into this breakdown. Then our availability, which we already talked about so given those inputs and our verify okr, to approve our slow pipeline creation time.

A

um What I'm, suggesting or proposing is a breakdown or a split of seven above seven maintenance and six feature issues planned. We've been planning about 20 issues per Milestone that might be a little high given holiday season that we're rolling into for a lot of us in Europe and North America.

A

But we've also got a few more folks onto the team who are coming up to speed and doing a great job of helping us break down these issues and work on these and deliver them so that we're delivering great outcomes for our customers so crossing my figures that 20 is not too ambitious today, as we have things planned out, we're at 11, 7 and 6., so I'll be looking to Caroline and Richard to help break down and try to move some bugs out de-prioritize those if we can we'll figure out other ways to mitigate those for customers.

A

So that's just a quick breakdown on 15 8 and walking through their cross-functional prioritization um in a couple of days. I'll drop another thread in there talking about what should be deliverable or what should be stretched for the Milestone. If you have any questions, you can definitely ping me in slack in Channel or add a comment to the planning issue. Thanks.