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

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 15.2 Kickoff - Verify:Pipeline Execution

Description

Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify

Issues Discussed:
Reduced cost factor for forks of public projects - https://gitlab.com/gitlab-org/gitlab/-/issues/346400
Running manual job from a pipeline throws generic error - https://gitlab.com/gitlab-org/gitlab/-/issues/352846
Specific messaging when .gitlab-ci.yml is missing`only: [merge requests] - https://gitlab.com/gitlab-org/gitlab/-/issues/273594
Define the workflow for users trying to run a pipeline with blocked shared runner access - https://gitlab.com/gitlab-org/gitlab/-/issues/352815

We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl

A

Hello welcome to the verified python execution, 15 2 kickoff. My name is james heimbach, product manager for the pipeline execution group here at git lab. As a reminder, this group is responsible for git lab ci pipelines, pipeline processing, as well as the category of merch trains. I'm joined by the pipeline execution product designer vedica, as always, and you'll find a link to the 15 to kickoff page with links to these items and the verify stage direction page with discussion of our future work. In the comments below the video.

A

You can always reach me at jheimbuk, gitlab.com or through comments on issues with the group pipeline execution label in the gitlab project. So during the 15-2 milestone, the theme that our group is working towards is better support for open source contributors who are using shared sas runners and our continued theme to work towards overall platform stability.

A

So, let's unpack that a little bit and talk about the goals that we have to support the themes, so the first one is focusing on work um to ensure the stability of the gitlab platform by meeting the slos for reliability and security issues.

A

Primarily, I've talked about this in the last three or four, probably kickoff, videos that we've done and we've been making really good progress in eliminating the backlog of those older things and getting new items uh scheduled into their target slos, um so that we're closing those at a quicker pace and in fifteen two. You can see in our verified p ones that we have three of those they're confidential issues, but the team is focused on those first and foremost within the milestone.

A

Our second goal is to reduce the csd minute consumption for contributors to the gitlab projects and open source projects. So we're really excited on june 1st to enable accumulation of ci cd minutes for all public projects on gitlab.com.

A

Since then, we've seen some contributors, especially to gitlab.com, using all of their monthly allotment of minutes within just a couple of days, um and that's not what we expected to happen so we're working on a fix for that quickly, specifically for the gitlab.com project, so that contributors to the project don't have to pay to do the contribution, and it raises the importance of this work for projects in the oss program.

A

The open source program, as well as just contributors to public projects, so to avoid that uh our focus in 15-2 is to redu use a reduced cost factor for public forks of public projects, as well as using a lower cost factor for forks of oss program projects.

A

So we're working on those two issues to make sure that we're not having a bad experience to contributers to public projects into open source program projects, and with that I'm going to hand it over to vitica to discuss some of the upcoming usability improvements that the team is exploring for later this year.

B

Thank you so much james, uh so this milestone will be focusing on three major issues. uh The first one of this is back and running manual. Job from uh pipeline throws generic 403 for non-validated users what's happening here is when new users who have not had a chance to validate their uh credit card yet try to run a pipeline in the project.

B

They see a message that prompts them to do so, but when they try to run a manual job, they are shown a 403 error and it doesn't tell them like what exactly has gone wrong. So we are going to fix that moving ahead to the next one. uh This one says: uh merge strains specific messaging when gitlab ci yaml is missing, uh only merge requests. So today we don't have any specific messages for when users try to use, merge trains and they don't have uh pipelines for pipeline for merge results enabled for that project.

B

Yet so we have to um surface some sort of error for that particular scenario. And lastly, the last issue that we'll focus on is defining the workflow for users trying to run a pipeline with blocked shared runner access.

B

So in one of the previous milestones, what we did was we introduced our capability to block share donor access on the admin side, but we are yet to figure out like um we haven't yet defined what users, whose access is blocked to shared runners, uh would see on the ui when they try to run a pipeline or a job, and that's all from my side. That's huge james.

A

Awesome, thank you vedica. um We're really excited for 15, too, and if any of these issues are interesting to you, please feel free to tag us in the issues thanks. So much.