GitLab GitLab Group Kickoffs - Verify:Pipeline Execution (formerly known as CI), 16 Jun 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab16.2 Kickoff - Verify:Pipeline Execution

Description

Delivering Fast Forward Merge trains for semi-linear history via Support merge train MR ref being created with r... (gitlab-org/gitlab#413103). Why? This is a standard merge method that users would love to be able to sequence and support with Merge Trains.

Improved usability of Pipeline Schedules via Show an error in Schedules UI when a scheduled ... (gitlab-org/gitlab#224958) and Input fields on Pipeline Schedules have differe... (gitlab-org/gitlab#391212) Why? Pipeline schedules are very loved featured and are used to drive automation and efficiency of scheduling pipelines and tasks. At GitLab we use these pipelines to perform several tasks, including generating release post entries! By making them easier to use and more intuitive we will support organizations efficiency with pipelines!

A

Hi, my name is Jackie Porter I'm, the acting product manager for pipeline execution, which is a group responsible for bridge trains, our pipelines, experiences and all the testing features that inside of gitlab, we are nested inside the verify stage, which is all about our CI capabilities. As we start to think about what we're hoping to accomplish. In 16.2, we have two main goals: delivering fast forward, merge trains with semi-linear history and optimizing. Our pipeline schedules experience which will help us drive efficiency of the whole gitlab CI use case.

A

So as we start to think about what it means to support fast forward, merge trains, you know merge methods in our merge trains functionality. We have to make sure that we're treating the merge commit uh in the in the merge results pipeline the correct way and also supporting automatic rebase with that. So we're able to make sure that these previous branches are being merged into the target branch and the right sequence to support fast forward. Merge methods pivoting over to our second main priority around a better experience related to UI, first pipeline schedules.

A

So today, when a pipeline schedule fails to be created, there's no sort of notification, no sort of information about it. So what we're hoping to implement in 16.2 is this Banner that allows people to understand that the last pipeline failed to create so that you can take an action on it. Secondarily, we're going to be thinking about making the page of pipeline schedules a little bit easier to follow and use so right now, there's various input fields for like variables and actual time and date, and those um aren't consistent.

A

The sizes aren't consistent and they crop different text. So in order to make that easier to use we're going to be improving that overall usability there well I'm super excited for 16.2. It's going to be an incredible relief for efficiency in using gitlab CI. If you have any questions, please reach out to apply reporter on these issues and effects.