GitLab 15.5 GitLab Kickoff, 15 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 15.5 Kickoff - Package:Package

Description

https://gitlab.com/gitlab-org/gitlab/-/issues/368535

A

Team, this is KDA product designer for the package stage and today I'm going to talk about what we're up to in Milestone 15.5.

A

So we'll talk about the container registry, First We are continuing our Focus to work on the container registry and migration, and this is something that the team's been working really hard on for a long time um and the reason why the migration is important is it opens up quite a lot of possibilities to make improvements such as usability improvements that customers have been requesting and that we would really like to make.

A

So it's super exciting that the migration is almost done so there's a few points here around the migration, we're also making some performance improvements for the cleanup policies, which is great onto the package registry. uh So today we have a feature for uh Pi, Pi and npm that if the package is not um found in gitlab it uh requested from the public registry um and we're currently working on the same for Maven.

A

This is a highly requested feature, and so we've been working on that since last Milestone and um one of the um at the moment those settings live at the admin level, which means you can't control them from an individual project or group, and uh one of the things that we want to do is give users a little bit more control over those settings.

A

um So uh what we're working on this Milestone is cascading namespace settings downwards. So that means, if I'm an admin and I um set the setting at the admin level. It can be overridden at the group level.

A

So in this Milestone we're working on bringing bringing those settings down into the group level and then we'll of course need the front end the UI, where the group owners can control it. So that means that the groups don't necessarily need to respect the admin settings, so hopefully that gives users a little bit more control over this new feature of request. Forwarding um another thing that we're working on yeah.

A

We have been working on the package cleanup policies for quite a long time, so we have a feature out currently where you can manage the storage used by package assets um and the next step will be adding quite a lot more rules around deleting actual packages.

A

um So we have some back-end work, this Milestone uh that uh creates a service that marks packages for deletion and that's the first step towards more uh options for cleanup policies.

A

um Another thing that we'll be doing this Milestone is adding the last downloaded date to the package registry UI. um So last Milestone we started recording When a package was last downloaded and the real benefit there is eventually you'll be able to set a cleanup policy. So if a package has not been pulled recently, you can allow that package to be automatically cleaned up so we're starting to make moves in that direction, but we're also going to add it to the UI.

A

So when you're looking at the UI, you can tell if the package is in use or not, um we have some additional front-end work to um continue work on the settings redesign, so we are continuously adding more settings and we're going to be um greatly expanding. The package registry cleanup policies in the future, so we have to like foundationally make sure that the settings can accommodate that the settings UI so there's some more work to be done there and some tidy up work uh around um improving some some copy.

A

um So yeah, that's uh that's what we're working on in in 15.5 from the research side, I will be continuing. The package touch Point interviews, so this is where we talk to users who are using the package registry, the container registry or the dependency proxy, and we're just really curious to hear about your workflow, your pain points.

A

um So if that's something that you're interested in participating in please reach out um and yeah any questions. Any comments, please let us know in the issue which I will uh attach to the body of this YouTube video thanks.