GitLab 13.12 Release Kickoff, 18 Apr 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.12 Kickoff - Release:Release

Description

Planning issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/62

A

Hi, my name is enrique lewinsky and I'm the senior product manager for the release stage here at get lab. Today, I want to walk through some of the really exciting stuff that we have planned for the 13.12 release you can follow along by going to the ci cd release group project issue number 62., so I'm going to start by talking about group level permission configuration for protected environments.

A

This is a request that we've heard from different organizations, especially those that are highly regulated and need different kinds of permissions for different kind of users throughout their pipelines.

A

um What we can normally say about environments is that there's different types of environments that we support and each environment needs different permission types, so we have, for example, a dev environment testing environment, where it's not exposed to users and basically anyone can deploy there. But when we're talking about staging in production environments, we need higher regulations in uh organizations where there are lots and lots of projects. Project level protected environments is just not sufficient enough. It's really hard to add specific permissions for every single project.

A

So the idea of group level permissions allows you to consolidate different projects under a specific group and allows you to give different permissions to that specific group, whether it be a maintainer role for that group, a developer role and so on, or you can explicitly give someone permissions to deploy to that environment.

A

Now when we started working on um this issue group level formations, we noticed that there's a previous issue that we um delivered. That is a blocking issue, so we may need to revert, um allow reporters to run jobs that deploy to an environment if they're explicitly listed listed and what this allowed you to do.

A

That was that, even if you were not a maintainer in a project, you were still allowed to push the deployments to production, and so we may need to revert that uh we're not entirely sure, but once we uh move forward with this group level, permissions we'll see how we can kind of still allow explicitly letting users deploy to production, but they will probably need an additional role.

A

The next issue that I wanted to talk about is adding event time steps to jobs and deployment web hooks, so we're going to start specifically to deployment web hooks and what we want to do is add additional metadata like timestamp or event timestamp. That will let you sort and filter and understand. What's going on in your web hooks which this information is currently not available.

A

The next issue that I want to kind of discuss is moving user lists to its own subpage of feature flags.

A

So if today you are a feature flag user, you can see that um on the feature flag list view which kind of looks like this today, there's a tab that allows you to view user lists and you can do different kind of operations there. You can create your own lists. You can edit them and user lists are really joined between different feature flags and what we want to do is kind of make it its own uh page.

A

So user list will move out of this tab like view, and it will become its own page that you can access independently.

A

That will make it much more convenient easily accessed it'll have its own url, and so on next thing that I that we're going to work on is making it more obvious that a request to deploy an environment has been requested successfully, and this is kind of going to look like this. So in your merger quest you're going to see a start environment, if you press it, you'll see the starting environment, working and eventually you'll also see a stop or stop environment button as well. So this is some usability improvements to make it more obvious.

A

What's going on in your pipelines,.

A

And the last thing that I want to talk about, um even though there's a lot of content is group level deployment, frequency, ci, cd charts, um which is uh on top of our door, four metrics, which we're continuously working on we've added um api for deployment frequency both on the project level and the group level and api for project and group level for lead time for changes. And now we also have charts for project level, deployment, frequency and lead time for changes.

A

And now we're introducing the first group level chart which is going to be for deployment. Frequency will be very similar to what we have on um on the project level. But it will have the group level data, so it will have aggregated data for all the different projects.

A

So it will look something like this. If you go to your under your group level, under ci cd.

A

You will be able to see a similar chart on the group level and maybe one more uh to go.

A

um The la another bonus point uh feature that we're going to be working on and this releases deploy free is remove a freeze period via ui, so we recently worked on allowing users to edit the freeze period in the ui and now we're adding also the option to delete so it'll. Look something like this.

A

You'll now have an option to remove a deploy freeze, um so it really gives you maximum focus ability, as you can see in the issue, there's a lot of things that I didn't talk about because of the lack of time, but you're welcome to view the issue and give us feedback or ping me on any of the issues or email me at elgolinsky. Kidmap.Com really excited for this upcoming release. It's going to be a great release and I'm looking forward to hearing feedback from you.