GitLab Pipeline Execution, 4 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Pipeline Execution 14.8 Refinement/Planning Kickoff

Description

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

Planning Issue (Internal Link): https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/83

A

18. uh deleted uh above 14 8, finally kickoff, um so the planning issue is out there for you to review uh it's in the pipeline execution uh project I'll link to upload the video high level. uh The theme around this issue or theme around this milestone is uh runner minute enforcement for those non-oss public projects.

A

um So some of the goals that are gonna build up to that theme or some of the goals for the milestone are hardening limits for cni minutes usage for projects created after that july, 17th date of 2021, and that is our number one uh or the only verified p1. That right now is planned. We do expect that some things roll over.

A

We also want to have a spike around identifying who can see ci minute usage, um and so that spike is up there if you're gonna take it take a peek at that. uh We just want to kind of consider who should be able to see that data, what they should be able to do with that data. So this is related to another issue.

A

That's going to be coming up later around defining some explicit policies around who can see those ci minutes what they can do with those as part of the ci admittance limits for the public projects, um so that spike leads into that. um The other goal for me for the milestone is to reduce our carryover of issues uh you can see and part of that is holidays. Part of that is engineering allocation.

A

We have definitely had more issues carrying over than we're getting done and that's not stopping us from planning a bunch of issues into the next milestone. uh So you can see in our board it's pretty light for what's already planned for 14.8, but we do expect a significant number of items in 14 7 to carry over as well um and so we'll be stack, ranking those as things move over, but definitely trust in that verify. P1 p2 p3, as you look for items to work on pulling from the left.

A

If everything to the right is already in a state where you can't uh can't move it along or help out, um so that covers uh the verified, p ones, uh we don't have any p ones that are front ends that are new in 14, eight we're continuing to look for more front-end work, especially around our okrs.

A

We talked about the spike, adding some more detail to a 403 message about um what somebody needs to do or why they would need a validated credit card for those actions. That is a back end issue.

A

Another back end issue is deciding this custom app decks targets, so hopefully we'll have some folks rolling off the engineering allocation back on the team on the back end, who can help with those uh and sam and abiel, and I continue to look for more front-end work, especially rather okr's, like I mentioned um so I'll link to this issue and from there you can get to the other issues below the video, as well as in the slack message that I will post here shortly. Thanks.