GitLab 15.0 GitLab Kickoff, 12 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 15.0 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:
https://gitlab.com/gitlab-org/gitlab/-/issues/345795 - Provide Visibility for shared runner usage for user namespaces.
https://gitlab.com/gitlab-org/gitlab/-/issues/355666 - Add Usage by Project graph and project table for SaaS runner usage to the group project page.
https://gitlab.com/gitlab-org/gitlab/-/issues/335968 - Show year in CI minutes usage graph
https://gitlab.com/gitlab-org/gitlab/-/issues/217718 - Make it easier to understand different merge request pipelines

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

A

Welcome to the verify pipeline execution, 15o kickoff, my name is james heimbach, product manager for the python execution group here at gitlab. As a reminder, the group is responsible for gitlab ci pipelines, pipeline processing, as well as the category of merge trains. I'm joined today by the pipeline execution uh product designer vitica in the 15-0 milestone.

A

We're focused on closing some vulnerability issues, improving our ci minutes visibility and our ci metering to assist in mitigating pipeline abuse on the platform you'll find links to the 15-0 kickoff page with links to these items in the verify stage direction page with discussion of our future work. In the comments below the video, you can always reach me at jay, heimbach at gitlab.com or through comments on the items with group pipeline execution label in the gitlab project.

A

I want to take a closer look at the goals that I mentioned in a little bit more detail. So in the 15-0 milestone, the team really has two main goals for our milestone. The first is to burn down some of our missed slo issues. Closing out issues like this in a timely manner will help us keep the gitlab platform stable and available for a broader user base.

A

Our second goal: I'm going to deep dive a little bit more on and that's to provide more visibility of shared runner usage. So this is ahead of our anticipated change on june 1st to accumulate minutes for all public projects in the same way that we've been doing it for projects that were created after july 17th of last year.

A

Right now, it can be really hard to track how many runner minutes a project is using, and it's even harder when you have a lot of projects that are running pipelines in a given month.

A

So with the changes that we're making you'll be able to see your namespaces project, shared runner usage in the usage quota screen and for any groups on the group group usage quota screen. So this will let you easily compare your runner usage to your ci minutes as we use a cost factor between those two so that you can start to plan better for your anticipated ci usage as those two things come together.

A

So while the team continues to focus on this, we have some great ux improvements coming our way as well and I'll pass it over to vitica to share her screen and show some of those off and talk through them.

B

Thank you so much james.

B

So um I will start actually with the um am I showing my screen change you already, so it's kind of confusing for me. Okay, thank.

A

You jobs to be done, paige for us, the pipeline for the pipeline.

B

Yeah, thank you so much so we are going to make some considerable amount of changes to the documented jobs to be done and just to give a very quick overview uh about what this is. So jdbs are a lens through which we observe markets. Customer needs, competitors and customer segments differently and by doing so, make innovation far more predictable and profitable, but in the context of piping execution.

B

What this helps us to do is it helps us understand your underlying motivations when you are performing certain actions on the product, and it helps us also to identify and validate different problem areas, but with time this gets, uh I mean it's important to keep them updated, so we'd be running some user researches and it might happen so we might reach out to a few of you to speak to uh so that we are able to make good refinements to our listed jobs, to be done.

B

That's one and, uh as james pointed out some interesting things that we are going to work on so james. I talked about about this issue which says: provide visibility for red, shared owner usage for user name spaces.

B

It's something that I had worked in the previous milestone on and uh there's a follow-up issue for this, which has been scheduled for an upcoming milestone, and this includes so since we are showing the charts as of today, uh we would be surfacing the user charts for uh usage by month, use it by project, but for this particular section, where uh there's a table that appears for all the projects that are using the shared runner and it also lists the ci cd minutes used um alongside.

B

We created a separate issue uh because we decided to take care of this as a part of a different iteration. So that's one thing that I'd be focusing on, and apart from that, a few things that I wanted to touch upon are some very interesting uh experience related improvements that you're going to make in 15.0 things that would be implementing the first one is. We are going to show you're in the ci minutes usage craft, so um we had worked on providing you with these chats, but there was still this debt that we had.

B

Are you expected that we had that we did not surface the um gears there and now it's much more convenient to select your and uh the month, the following month, making it much more usable for you, that's one and another one that I'm very excited about. Is this issue which says make it easier to understand and differentiate, merge request pipelines because it does so much more than we had actually envisioned through the problem statement. So the solution here it talks about uh how we are going to slowly remove. Okay, my internet connection is unstable.

B

I know that. uh Have you slowly going to remove the detached label and change that to merge request label. uh So, in short, what we're trying to do here is we're going to make all the labels the existing labels more human readable and also introduce a few more labels to make it very clear, like what's the purpose of this pipeline that you're looking at so there's, not anything left to guessing and further investigation and yeah. That's all the update that I have from uh ux back to you, james.

A

Thank you, vedica. I'm really excited about those updated labels. Detached has never made sense to me, so I think this would be a lot more clear about what that pipeline is where it's running, where it's heading so that'll be exciting for our users. I'm really excited too about breaking down that project usage between ci minutes and shared runner minutes. I know, as our runner team looks, to expand the types of runners that'll be a super important way for users, so they're clear about what different type of runner, how those minutes accumulated for their different projects.

A

So it's a super, exciting iteration, so we are very excited for 15 0.. We love these major milestones. If any of these issues are interesting to, you feel free to tag either of us in those issues. Thanks so much.