GitLab Pipeline Execution, 1 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Pipeline Execution 14.10 Planning / Refinement kickoff

Description

This video walks through the theme and goals for the 14.10 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/88

A

I wanted to share the 1410 planning issue as we're kicking off refinement. So this is the pipeline execution. 1410, refinement, kickoff um I'll, share a link to the issue uh below and then the select message I post with the recording uh for the team so 1410, our big theme is really getting our ci minutes, work unblocked uh and then improving the user experience for commits without ci.

A

So some of the goals for the milestone, some of this is or the big one is really delivering any of those remaining blockers that originated with group utilization for the ci minutes work around the oss plan, making sure the plan is populated so that we can start to move projects into the oss plan that are public projects today to make sure we're treating those different from public non-oss program plans and then the next one is delivering those 60kr issues between such issues and security issues in the verify p p1s.

A

We have a couple of confidential issues uh that are security issues um that are uh important for us to deliver uh in this next milestone and then within sus. We have four of these uh three of them. Seven ones and ones have two: uh I know vedica has most of them wrapped up, so they should be in planning breakdown.

A

There might be one still in design um when I last looked, uh but if you can jump in there and make sure that we have called out any back-end prerequisite work for the front-end work that needs to get done, that we scoped and refined those well so they're ready to move forward.

A

I also want to call out that we do have no current ci builds metadata issues as part of the milestone that epic is slated for q1. So far that epic is empty. It does have, or is part of a parent epic, that's slated for cube two, um so maybe the work that is in there will be all wrapped up, and so there's just not issues that are attached to the epic, uh so I'll ping gregorish. On that to make sure that we're making progress there, I didn't see any infra dev issues.

A

We do have one feature flag rollout uh in the milestone one flaky spec to fix. Richard um is sorry calling out richard. There is one that is assigned flaky speck. I didn't find any other failure issues, but maybe I missed one of the tags or one of the labels. Rather so, if you want to take a look and add any quality tests that we need to add there, um and then we do have one community contribution so far.

A

I did just see in slack before I started this mark ping about another, mr that was coming through. So maybe we'll get an issue spun up for that. If we do take it uh and marcel, I didn't see any docs improvements already scheduled for the milestone. If there are things that we want to pull in, we can surface them here.

A

So those are some of the highlights uh around the theme and the goals for the milestone.

A

uh So go ahead, jump in uh to the board itself, which you can get to and I'll add a link for as well and start going through that planning breakdown list which there's nine of them in there so far and let's get those uh refined and put weight on them make sure we have both front end and backhand taken care of if need be, split out issues where appropriate, uh we'll get those moved over into ready for dev and get moving on the milestone thanks. So much.