GitLab 15.6 GitLab Kickoff, 13 Oct 2022

Previous Meeting

⏯

youtube image

►

From YouTube: GitLab 15.6 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:
UI for Inbound CI_JOB_TOKEN - https://gitlab.com/gitlab-org/gitlab/-/issues/375782
Configure CI/CD quota - https://gitlab.com/gitlab-org/gitlab/-/issues/362287
Improve workflow for finding a project to set quota - https://gitlab.com/gitlab-org/gitlab/-/issues/366929

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

A

Hi welcome to the verified pipeline execution, 15 6 kickoff. My name is James heinbach product manager for the pipeline execution group here at gitlab. As a reminder, this group is responsible for gitlab CI pipelines, pipeline processing, as well as the category of merch trains and I'm joined today, as always by our product. Designer vitica you'll find a link to the 156 kickoff page with links to these items and the verify stage, Direction page with discussion of our larger future work. In the comments below the video.

A

You can always reach me at jheimbook, gitlab.com or by tagging me in a comment on any of the issues with group pipeline execution as the label in the gitlab project. So I'm already sharing our planning issue and you can see our theme. Here is improving pipeline security, uh so we have a couple of goals for our Milestone.

A

The first is uh meeting our reliability slos for all of our verified peabots and as a reminder, we use the verified P1 label to indicate top priority issues, things that we really want to deliver and that might be due to service level objectives um that we're trying to hit around bugs or security or availability type of issues, and that really ensures that we have a reliable and stable platform which maps to our larger investment theme for the year across all the product uh for a gitlab hosted first investment theme, um so we have a number of verified p1s.

A

A few of those are confidential um and the one that we're going to really dig into today, both vedica and I, is the new interface for the inbound CI job token, um and that is our next goal- is delivering the next issues in Phase, 1.1 of RCI, gitlab or sorry, CI, job, token, workflow, epic and that's creating the new interface. For that inbound token.

A

So back in 144 we set up and created uh the secure token for external, so you can decide which jobs, your CI job, token or sorry, which projects or CI job token could work with to restrict that access. This flips that to restrict inbound tokens, so only tokens for the projects that you allow would have any sort of access into your project.

A

So this creates the UI for that and both of these things are- or this is anticipation of making security not only default but only option uh as in 160, and so we'll have a deprecation notice soon about that of the insecure or not insecure option. But the non-limited option is not available at all for projects and that will be in 160..

A

um So those are the the themes and the big goals. uh Some of the issues that I wanted to talk through today and so now I'll hand it over to vedica to discuss some of the upcoming usability improvements. The team is exploring for later this year.

B

Thank you, James um yeah, first I would, even, though, we're making uh mostly making progress on the um configuring cicd quota for groups, uh projects under crews in this Milestone, but since teams just talked about the ca job token inbound, workflow, I thought I would just like give a quick glimpse of that and talk about it with you. So um yeah um as you can see, there's a whole new workflow that has been added to this page to the section.

B

um That is, uh that would allow you to kind of um like check, which are the projects that have access to your projects using their CI job tokens, and you can really control that from here. You can also remove projects um or give them permission um like. As per your requirement.

B

um We still have the outbound one like in this proposal, because we did not want to make this particular like implementation of breaking change, so that's going to be there for a while and then slowly that would be moved out yeah. This is that, and we would love to hear more about, like here's, some feedback about this once this is rolled out now. Moving on to configuring cicd quota for projects under groups- um I talked about this earlier as well in the previous kickoff uh that we first worked on configuring.

B

The quota for projects under name spaces. That was our first step and we took that step because, uh like we first wanted to make sure that we are moving in the right direction and we just thought it's, it's a good first step to start with name spaces username spaces rather than groups.

B

Now um it will be working on the design for the group part of this exercise, and uh since we have some information from the previous validation resource that we ran for the previous solution, we would be making some correction to the workflow, um and we are also pairing this effort with another issue.

B

So in the next tab, you see that there's this issue that says improve workflow for finding a product to set code offer one of the things that we learned from our validation research is that uh users do not have a lot of products directly under their username space, but that's very different for our groups, of course. So, just because, just before we uh move the solution to the group level, we want to make sure that our users are able to find uh projects from a long list of projects. So we would also be improving.

B

um This particular feature that we have for searching for a project from a very long list and then uh setting a quota or editing a quota for that now. Once these two proposals are in place, we would be taking them to validate with our users, of course, and that's all from me.

A

Thanks vetica we're really excited for 15 6.. uh If any of these issues are interesting to, you uh feel free to tag us uh in those issues or you can reach out to me anytime, at jheimbuck gitlab.com thanks.