GitLab 14.9 Release Kickoff, 8 Feb 2022

Previous Meeting

⏯

youtube image

►

From YouTube: GitLab 14.9 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/groups/gitlab-org/-/epics/5653
https://gitlab.com/gitlab-org/gitlab/-/issues/346796
https://gitlab.com/gitlab-org/gitlab/-/issues/330850
https://gitlab.com/gitlab-org/gitlab/-/issues/340593
https://gitlab.com/gitlab-org/gitlab/-/issues/345795

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, 14.9 kickoff, my name is james heimbach, product manager, for the pipeline execution group. Here at gitlab and as a reminder, this group is responsible for gitlab ci, such as pipelines, pipeline processing, as well as the category of merge strains, I'm joined by the pipeline execution product designer vitica and in 1490 we're focused on ci minutes, visibility, still ci minute metering for open source projects and that helps us with mitigating pipeline abuse as well.

A

You'll find a link to the 149 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 jheimbach, gitlab.com or through comments on any issues with the group pipeline execution label in the gitlab project.

A

So I want to focus in and I'm already sharing our planning issue on our big theme and our goals for this milestone. So we have some ci minutes. Work we've been talking about that for a while on these kickoff calls we're a little blocked right now, and so our goal for our theme for this milestone is to get ourselves unblocked. So we can keep moving forward and it hardened those ci limits to help mitigate the abuse and start actually counting minutes being used by projects.

A

The other is to improve our customer experience around some of the pipeline and the mr widgets.

A

So as part of that, we have a couple of goals for the milestone to speak to the first two there's a couple of issues in group utilization that are blocking us we're going to pick those up and work on those so that we can get those new oss plans put into place or the new oss plan put into place and then start assigning projects to that, so that we can count those oss project minutes uh the way that we need to to implement the broader limits.

A

And then we have three sus okr issues, sus being system, usability, score and okr are objective and key results. So for q1 we have a broad okay, our goal about burning down a bunch of those sus issues, um and so those are our two big goals for the milestone: uh we're keeping the epic that we've referenced in the 14.8 kickoff, that is tracking the ci minute usage work up to date and I'll link to that below this.

A

If you want to continue to follow along on our efforts there- and I mentioned our other goal- is improving that customer experience with the pipeline and the mr widgets on the mr page and that a big focus for the team. This quarter is really getting some of those high severity slush issues taken care of so we'll be addressing three of those in this milestone and I'm going to hand it off to vitica who is going to walk through and talk about those and the impact that they'll make so I'll.

A

Stop my share and hand it off.

B

B

All right so after three system usability score impacting issues. Here's the first one and this one talks about updating updating text on the protected manual job page so what's happening today is uh when a user who doesn't have a permission to run a protected manual job when they land on the screen. They are, they don't uh like. We don't communicate very clearly to them like what the problem is. Why is it that they cannot run this job and that's what we want to fix uh through this issue?

B

The designs are here like we are communicating clearly that hey um like you, do not have the permission to run the job on this environment and reach out to a project mem member allowed to deploy to the environment and there's that then the next one says improve mr widget, pointing when pipeline is skipped and merging is allowed.

B

So when you go to the settings and you select uh when the merge check for a project allows merging when skipped when pipelines are skipped, then what you see on the widgets? It does not really communicate very clearly to you like uh what the situation of the pipeline says. The skipped pipeline is considered success, yes, but there's no other affordance on the widget. That tells you that the pipeline has been skipped and that's how you have arrived at the current uh state of the pipeline.

B

So we want to make those things very clear and what we are doing here is. uh We are changing the variant for the button treatment. We are making it more clear that by facing this morning, I can hear uh and just like making it like sorry. Why is it not moving to the next one yeah and then changing the text on the confirmation model to something which is uh more explanatory, that uh that communicates to the user? Is that the pipeline? For that particular uh change?

B

It was kept and they should keep that in mind before merging the change. The last one that we are going to implement in this milestone is making group level usage quota page more discoverable.

B

So today we have the usage quota uh information all stored under uh the group settings in the usage quota page, but not many users were able to point to that when we conducted a research.

B

So based on our on the inside that we received from a recent ux scorecard research, we created this issue and now what we are doing is we are providing more visibility to that page through a very small and pouring solution, which is providing a link in the analytics tab and that's how we are like dealing with this uh today and lastly, another issue that I want to talk about, which is not a sauce, but it's something that we are working on in this quarter, is uh providing visibility for shared runner usage for user name spaces.

B

So this is something that we are working on in 14.8 for the group level and we want to give a feature that an equivalent feature for username spaces as well. So uh if you do not have a group- and you have just projects under your namespace and you just want to go and have a look at the shared runner usage for those- you should be able to do that and that's all from your excite back to you. James thanks.

A

So we're so excited for 14.9. If any of these issues are interesting to, you feel free to tag us in those issues or on any issues that are backlogged. Thank you.