Many projects depend on a growing number of packages that must be fetched from external sources with each build. This slows down build times and introduces availability issues into the supply chain. For organizations, this presents a critical problem. By providing a mechanism for storing and accessing external packages, we enable faster and more reliable builds.
In addition, the Dependency Proxy will work hand-in-hand with the planned Dependency Firewall, which will help to prevent any unknown or unverified providers from introducing potential security vulnerabilities.
This page is maintained by the Product Manager for Package, Tim Rizzi (E-mail)
We have launched the MVC of the dependency proxy with limited availability. gitlab-#78 will update gitlab.com to use Puma, making the Dependency Proxy available for all public projects. Prior to that, we are prioritizing gitlab-#37967, which will focus on testing, documentation and operational support of the Dependency Proxy. As part of that work, we will be sharing examples, demos and other material to help users better leverage this valuable feature.
This category is currently at the "Minimal" maturity level, and our next maturity target is Viable (see our definitions of maturity levels). Key deliverables to achieve this are:
Artifactory is the leader in this category. They offer 'remote repositories' which serve as a caching repository for various package manager integrations. Utilizing the command line, API or a user interface, a user may create policies and control caching and proxying behavior. A Docker image may be requested from a remote repository on demand and if no content is available it will be fetched and cached according to the user's policies. In addition, they offer support for many of major packaging formats in use today. For storage optimization, they offer check-sum based storage, deduplication, copying, moving and deletion of files.
However, since they have focused on solving all possible usecases, there is room for simplification and design improvements. We believe this will allow GitLab to provide a more accessible and easier-to-navigate solution. In addition, we provide added value by combining this with our own CI/CD services, improving speed and having everything on-premise.
The top customer success issue is gitlab-#11582, which will introduce authentication and allow users to leverage the Dependency Proxy with private projects.
Our top internal customer is the Distribution team, which would like to avoid relying on external sources for downloading dependencies. gitlab-distribution#496 will deploy Puma to GitLab.com and allow them to begin using the Dependency Proxy for images sourced from DockerHub.
Our top vision item is gitlab-#11680, which will introduce search and make items in the Dependency Proxy easier to discover.