GitLab GitLab Group Kickoffs - Package:Package Registry, 10 Aug 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 14 3 Kickoff Package Package

Description

Check out the planning issue here: https://gitlab.com/gitlab-org/gitlab/-/issues/336464

A

Hello, I'm tim, I'm the pm for the package stage here at get lab, and today I was hoping to review a few of the issues that we have planned for milestone. 14.3. uh We generally look at p1. These are issues that we're making strong commitments to for the milestone, and then we also additionally set aside some stretch, goals um that are if we can make through the p1 issues. We will tackle these as well, okay.

A

So the first theme that I think would be important to touch on is the dependency proxy right now you can use this feature to proxy and cache container images from docker hub, but right now the cache is just piling up. We don't have a time to life policy, so one thing that we'll be doing is implementing a policy that says every 90 days, just clear the cash for the dependency proxy. This will help reduce the total amount of storage used.

A

It will also help, as we start to expand this feature, to cover support for additional container registries like amazon's, ecr or as well as other package repositories like the public npm registry, so having a ttl policy for the dependency proxy thing is, if you navigate to the dependency proxy user interface, now you you pretty much just see an endpoint for how you to download images. Really. What we want to do is display the information about what container images or whatever dependencies we'll add. Support for in the future have been proxied and cached.

A

So adding a graphql query for the dependency proxy will allow us to expose that front end in future milestones. So what really? What we're looking for is what information can we add about the manifest?

A

What information can we add about the actual blob of the container image and what settings can we expose there so really starting to make the user interface for the dependency proxy more useful for those of you who are using it?

A

This next issue is a feature flag rollout, which normally we don't highlight, but I think it's a great one to highlight for this milestone, so we will be. We've had a community contribution that we've been working on or with a community member for the past, several milestones to add support for debian packages, so in milestone, 14.3 we're actually going to roll out support for this and make it generally available.

A

On.Com and it'll be included in the milestone for self-managed instances, so you'll be able to publish and install dbm packages using your project as a as a package repository and then two issues that I thought would be helpful to highlight quickly.

A

um Just right now we have some data for uh pi pi that is exposed in the graphql endpoint, but it's not exposed in the front end, so just making sure that any data that we have like the gitlab branch and commit data or pipeline data actually shows up for pi pi and uh for composer as well we're in a similar situation. So, if you're, using either of these two package manager formats in 14.3 you'll, start to see additional data metadata about your builds and pipelines as well.

A

Okay, this is a subset of the issues, but these are some of the ones I thought would be helpful to highlight if you have any questions, feel free to reach out and feel free to open an issue and ping me directly. If not, I look forward to collaborating with you. Thank.

A