GitLab Package Group, 16 Jan 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 12.8 Kickoff - Package

Description

- Leverage Docker tag expiration policies at repository level
- Improved performance of the delete API for the Container Registry front end
- Improved performance for the GitLab Container Registry garbage collect algorithm for S3
- Build, publish and share packages to the GitLab NuGet (.NET) Repository

A

Hello, I'm Tim I'm, the product manager, I, could lab for the package stage and today I'm going to be talking to you about our upcoming issues scheduled for milestone, 12.8, which is scheduled for release on February 22nd 2020. There's four issues I'm really excited to talk to you about today. The first is leverage docker tag, expiration policies at the repository level. This issue is a follow-up to last milestone. We built docker tag expiration policies at the project level. This will enable it at the docker repository level.

A

So, for example, if I click on this UI, you can see I'm on the container registry user interface and at the repository level. I now have the ability to enable and disable policies and then I have the ability to set them both the interval to schedule at which they should run the number of tags to retain and which tags to expire, and you could use reg X here to set any to match any pattern. You'd like really excited to launch this feature. I should announce that this is only for new projects.

A

To begin with, we'll be working on how to extend this to existing projects in the future.

A

The next item is improved performance of the delete, a PI API for the container registry front-end. So this is fixing a stability bug and it's really important. It has definitely impacted the performance of the container registry UI and improving. This will improve load times and stability of the get lab application. So what are we talking about in the container registry UI? This is I, have here a repository repository with a set of tags and, if I were to delete these tags, the delete API that we're using is is route is quite slow.

A

It's one of the slowest in the entire gitlab application, so we'll be addressing this, which will greatly improve the overall performance of the application of end of the container registry.

A

Next, we're talking about improved performance of the container registry, garbage collection algorithm for s3, so lots of performance improvements scheduled for this milestone.

A

So this is for, if beyond just deleting images or tags in the UI, this is for actually cleaning them up using garbage collection from from s3. We've made a lot of great progress over the past couple of milestones on this issue, and so far we've done made a lot of optimizations.

A

The final change changes will be making in twelve eight is to actually make bench beyond just benchmarking and performance testing we'll be making sure that this that these changes can scale up to the levels of our enterprise customers and get lab itself really looking forward to releasing this change and we're so far we're seeing orders of magnitude improvement in performance times and finally, I'm really excited to say that we will be releasing the get lab nougat repository to enable dotnet developers to use git lab as a as a private nougat remote.

A

So this will allow them to configure the nougat configure nougat to add get lab as a remote you'll, be able to authenticate using your git lab username and personal access token, and we'll support, publishing installing and deleting packages all all from good lab and we'll have a user interface. You can see here it's very similar to what we have for the rest of our packaged registry items.

A

Okay, look! That's it for now! Looking forward to this release and getting these features in your hand, if you have any questions, please feel reach out to me at t-- rysiek at lab, calm.