Buildkite Package Registries
Scale out asset management for faster builds and deployments across any ecosystem with Buildkite Package Registries. Secure your supply chain and avoid the bottlenecks of poorly managed and insecure dependencies.
Package Registries allows you to:
Manage artifacts and packages from Buildkite Pipelines, as well as other CI/CD applications that require artifact management.
Provide registries to store your packages and other package-like file formats such as container images and Terraform modules.
As well as storing a collection of packages, a registry also surfaces metadata or attributes associated with a package, such as the package's description, version, contents (files and directories), checksum details, distribution type, dependencies, and so on.
Customers on legacy Buildkite plans can enable Package Registries through the Organization Settings page.
Buildkite Package Registries was previously called Buildkite Packages.
Get started
Run through the Getting started tutorial for a step-by-step guide on how to use Buildkite Package Registries.
If you're familiar with the basics, explore how to use registries for each of Buildkite Package Registries' supported package ecosystems:
Alpine (apk)
Container (Docker)
Debian/Ubuntu (deb)
📦 Files (generic)
Helm (OCI)
Helm
Java (Maven)
Java (Gradle)
JavaScript (npm)
Python (PyPI)
Red Hat (RPM)
Ruby (RubyGems)
Terraform (modules)
Learn more about how to:
- Work with registries in Manage registries.
- Manage access to your registries in User, team, and registry permissions.
- Configure your own private storage for Buildkite Package Registries in Private storage.