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

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 14.5 Kickoff - Verify:Pipeline Execution

Description

Welcome to Verify Pipeline Execution14.5 Kick Off! This group is responsible for GitLab CI, such as pipelines, pipeline processing, as well as the category of Merge Trains. In 14.5 we are focused on CI minutes visibility and implementing various control mechanisms for the pipeline permissions.

A

Welcome to the verify pipeline execution, 14.5 kickoff, my name is jackie porter, acting product manager, pe group here at git lab and as a reminder, this group is responsible for all things: gitlab ci, like pipeline processing pipelines, as well as the category of merge trains. I'm joined here by the pe product, designer vitica and in 14.5.

A

We're really focused on a couple of top priority items related to ci minutes visibility, as well as implementing various control mechanisms for pipeline permissions. The first issue that we have queued up is related to ci minutes and it's recalculating uh lazy loading of ci minutes on a monthly basis. This is tied to our uh deprecation of the legacy ci minutes effort that we've been working on for our past couple of milestones.

A

So we're super fortunate to be wrapping up this effort and excited that our users will have a more consistent experience with ci minutes.

A

Another big focus for ci minutes is enabling our back end for ci usage and historical data on the group usage quota page so in 14.6 we're hoping to implement the front end for this effort, but in 14.5 we're adding a graphql endpoint to enable this experience.

A

Another top focus for us in 14.5 is around pipeline permissions and security, which will be enhanced by two issues. The first one is guest access for jobs, which is allowing a guest to view job data but limited subset. This will help unblock one of our refactor experiences of moving the front end of the jobs page to view in graphql.

A

The second issue is around exposing job scope, data in the ci job token api, which will allow users to then introspect that information to see if the flag is enabled across all of our projects or in a group. We recently delivered the secure ci job token workflow in 14.4 it's default and to be disabled for projects, but this will help users know and be able to see whether or not you can have this feature enabled in your projects.

A

uh Vitica is also working on several features and design issues related to a wide variety of scope, including job logs and expanding our ci job token. So I'll pass it off to her to talk about her design work in 14.5.

B

Thank you so much jackie, so the design works that I'm doing for um 14.5 the first one of that is adding progressive loading to job logs. So today, what's happening is develop.

B

Developers want to view the complete sha block to have full context of about a job, but now, as of today, they can only do it by clicking on the raw log file if the log is over 0.5 mb.

B

So what we are trying to do here is we are trying to add an ability to progressively load the log section, so we can show the full log on the ui and without making developers go and download the raw logs and as we scroll the logs, they would load in chunks and in chunks that we know that we can process.

B

Of course, so that's a constraint, um yeah and the next one is configure job token scope at group level so for a private project to be accessible via ci job to it must be added to the law list of the originating project. Now this could become very cumbersome if an organization has many different projects and what they would want to.

B

The kind of control that I would want to have. There is for those projects to be accessible from each other, and currently the user needs to add each target project to the allow list of the origin project. Now to solve this problem, we are trying to perhaps enable the ci job token scope at group.

B

Level next one is add: settings for disabling public pipelines in the api. So by introducing this settings, uh what will the problem that we'll solve is so users today? They do not want to have anyone looking at their job blocks or projects, and that's very obvious, because they could have some sensitive data, such as the ssh key secrets, etc. So we are adding a setting so that they could disable public pipelines in the api.

B

And the last one is uh provide links to the failed pipelines from analytics cicd in project. So we did a research recently, and one of the findings were that even the user users are able to see like what's happening um like the very superficial performance of their pipelines, they're not able to drill down from the analytics page itself. uh They have to get back to the pipelines and job space to understand. Where is it that things are going wrong?

B

So what we would want to try to do here is provide a link to the failed pipelines from the analytics ci cd page itself, and that's all.

A

Thank you so much fitika for sharing all of the work that you're going to be taking on in 14.5 super excited about some of these features, they're really going to help our users and everyone leverage get a lot better.

A

One of the things that you were working on in a prior milestone was around a usability challenge in creating more space in the pipeline index page. So in this milestone, we're going to be actually rendering this work and it will allow us to make additional enhancements down the road.

A

You did a really great job, putting together this proposal and gathering feedback from the internal engineers, as well as applying user insights. So um we're really excited after about learning how challenging it was for our users to effectively leverage the pipeline index page to create more space to then and incrementally add more features. So thank you for sure and yeah.

B

Just to add to this jacket that uh we also have a solution, validation schedule for this, so we would be also taking feedback from our users as to how they're liking the new uh rearrange in the layout once this is in place. So yeah excited about that. It's.

A

Going to be so good, we're really excited for 14.5. If any of these issues are interesting to, you feel free to give us a tag and any of them thanks again.