GitLab Pipeline Execution, 18 Feb 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Pipeline Execution 15.11 Refinement Kickoff Planning

Description

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

The MM.m planning issue can be found here:

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

Breaking Changes/Removals coming in 16.0 - https://gitlab.com/groups/gitlab-org/-/issues/?sort=created_date&state=opened&label_name%5B%5D=group%3A%3Apipeline%20execution&label_name%5B%5D=deprecation&milestone_title=16.0&first_page_size=100

A

Hey folks, I wanted to record a walkthrough of the 1511 pipeline execution planning issue. uh This could be the last kickoff that I record uh certificate as we start planning for the issue and refining the issues uh and we're planning them out and we're finding the issues in the Milestone.

A

um So 1511 is um the release that will uh release in April, I, believe um and so we're going to be starting, doing, refinement on this in March. uh So for the issues that are already in the Milestone, um the theme that I pulled out is better scheduled pipeline experience.

A

um Some of the goals for that are a couple of bugs that we have around not being able to see easily that failed or scheduled pipelines rather aren't failing. um So we have a couple of different uh bugs in here showing an error in the schedules you buy um so that you could easily be among your scheduled pipelines, which ones are failing or which ones have had a failure most recently um and then no notifications for failed, scheduled pipeline.

A

The MVC for this is to send an email on that fail pipeline calling out the video schedule pipeline is failing. um That might end up being a little painful for the user, but it will be a good signal to them that your scheduled pipeline is failing. um So those are the two bugs that lead up to that goal.

A

um The other uh goal that I have for us for the Milestone is making progress on CI Gap merge that we have a couple of issues. The first is what we've broken out of that very popular issue: around High mounts and cancellation. The after script is not running. We've broken out the cancellation uh use case and ensuring that a canceled when a pipeline data canceled that those jobs or the chemical job runs as after script.

A

um Always this is a lot easier than the timeout, because we know that we've got connection to the runner, so we can execute that after script on that Runner and then the other is the spike around figuring out the level of effort to build out the path forward. Merge support for merge trains, the object, realignment issue that we've identified as the blocker is also in the Milestone.

A

um This issue, which I'll go ahead and open up. um So this is all also in the Milestone. I would call this a stretch in the Milestone. The primary focus really around the merge trains is going to be.

A

The spike of understanding is that still the right thing to go do is all of the work called out in that issue to make sure that we understand what we really need to do to execute on The Fast Forward merge, because that's a very popular open issue and a feature that we should Implement to advance the merge chains, category and feature set for better user experience overall, um so we didn't have any verified p1s, any Force prioritization, except one infrastructure issues.

A

As of this recording, so I have bumped up those two uh ensure after script and the level of effort to the verify P1. um There are no imperative like I mentioned, and some verified p2s in there uh are listed here.

A

uh No bugs of note that aren't already a verified, P1 or P2 um I didn't see any feature flag, quality tests or docs improvements specifically called out in the issues that are scheduled um and the other thing I want to call out that isn't in uh or scheduled for the Milestone are the uh deprecations or removals that are coming in 160, and so we may want to take advantage of a lighter Milestone planned milestone in 1511 to get spikes started or even get implementation started on those removals, get them behind a feature flag so that when 16 are rolled out, we can make sure that we hit those dates that we've already told people we're going to be removing and changing those things.

A

The inbound CI job token will be default. The other workflow will be gone. um There's the rest of them are totally is getting me right now, but I will add them to this issue and link to them in the video description. um So that is uh the kickoff for 1511, refinement and planning thanks. So much cheers.