GitLab GitLab Group Kickoffs - Verify:Pipeline Execution (formerly known as CI), 2 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Gitlab 14.7 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/337245
https://gitlab.com/gitlab-org/gitlab/-/issues/346399
https://gitlab.com/gitlab-org/gitlab/-/issues/300663
https://gitlab.com/gitlab-org/gitlab/-/issues/346298
https://gitlab.com/gitlab-org/gitlab/-/issues/293862
https://gitlab.com/gitlab-org/gitlab/-/issues/329787

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.7 kickoff, my name is james heimbach, product manager for the pipeline execution group here at gitlab. As a reminder, this group is responsible for good lab ci, such as pipelines, pipeline processing, as well as the category merge trains.

A

I am joined today by the pipeline execution product designer vitica and in 147, we're focused on ci minute visibility and the ci minute metering for oss projects that will also help us mitigate pipeline abuse by cryptominers you'll find a link to the 14 7 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 items with group pipeline execution label in the gitlab project.

A

So I'm sharing our planning issue already, and I wanted to talk through a little bit of the key features that we're going to be working on are some of the issues we'll be working on. First is hardening the ci limit for pipeline projects.

A

And we've talked about this issue previously and something that we've been working on to implement the new limits to further mitigate crypto mining abuse and ensure that reliability of the sas platform for oss users stays as rock solid as possible.

A

Another issue in that same vein is separating open source projects and standard free projects, their cost factors between those that's going to better enable us to serve those oss projects and their maintainers by providing a higher limit of minutes than on just a free project on gitlab.com.

A

Another top focus for us during this milestone is going to be to further explore use cases for the ci job token, uh through customer interviews and if you're currently utilizing that token or running into limitations with it.

A

I would be happy to chat with you about those problems that you're running into um you can open a discussion in the issue that I'll link in the video in the comments below the video or you can always email me at jheimbug at gitlab.com and vedica is also working on some interesting work related to items around merge stream usability and some of our token security related features that we talked about so I'll head it over to vitica.

B

Thanks james, so keeping in mind that we have holiday season upon us, I have set less ambitious goals for myself for this milestone and impactful. Nonetheless, all right, so the items that I would be focusing on for this particular milestone are uh just give me a moment to open my links for you.

B

All right, I'm ready to share my screen. There you go okay, the first one is regular. Merge button shows up when merge stream is enabled and pipe in for merge request is waiting on a manual action. uh It's an odd behavior that uh when these settings are enabled- and the merge request is waiting on a manual action, the merge widget shows uh just merge button. Instead, what it should be showing is start and or add to more stream, depending on what the uh situation with the moisture in is.

B

So that's what we are going to be fixing using this uh like through this issue. The next one is enable a ci to come permission flow for bots to work across dot com and other shared instance securely.

B

So we are trying to work on a workflow um such that products would be able to give access to specific pot users, and we want to make sure that this whole flow uh keeps it like. We do this keeping in mind that the security of the project is intact, such that any other project should not be able to access a different project's token, using this part.

B

So another impact that this work is going to have is on the workflow um for a feature which was to secure ci job token at project level, something that we had very recently introduced, but we'll keep in mind that whatever we, uh whatever solution, we come up with. We do not disrupt like the existing settings for users. Instead, we build on top of that another one is add filters and search on jobs, page for status and job name.

B

um So this is something that was uh designed for a very long time and we finally have the bandwidth to work on this. So on the pipeline index page, we provide a bunch of filters using which you can search for a given pipeline. We want to bring in a similar functionality on the jobs index page as well, and we would obviously not replicate the entire experience, but we will take into account the context here.

B

The last one is, it says, cannot create, merge, request pipeline if no pipeline ever ran. So what happens here is when, if a project has much equals pipeline configured, but for some reason it could be just any reason that the multicast pipeline uh was not started.

B

There is no manual away that we provide to users today uh so that they could just go and create a new pipeline so solution that we are proposing the tentative solution that we're proposing here is, we would show a run pipeline button to users if in case, uh this situation happens, but there would also be certain situations where we would not surface the button, which is, uh let's say if there is no configuration piping configuration that exists for that project and um in case there is no pipeline which is configured for that particular branch on which uh this change is happening, and that is all from my site back to you.

B

James thank.

A

You I'm really excited that, even while we're continuing to work on some of these really hard back end type problems that don't have a lot of user visibility that we're able to work on these types of issues that really reduce friction in the workflow for users who are trying to utilize gitlab ci. It's really exciting, um so we're so excited for gitlab 14.7 to come out. If any of these issues are interesting to, you feel free to give us a tag and any of those issues thanks.