Artifact Registries and Versioned Builds
An artifact is the packaged, ready-to-run output of a build — the exact thing that gets deployed. An artifact registry is the secure, organised store where every version of that package is kept.
Storing versioned artefacts is what makes reliable rollbacks and audits possible.
Why Versioning Matters
Each build is given a unique version number and stored, unchanged, in the registry. We always know exactly what is running in production and can redeploy any previous version on demand.
- Reliable rollbacks to any earlier version.
- A clear audit trail of what was released and when.
- Confidence that what we tested is exactly what we deploy.
Build Once, Deploy Many Times
A core principle is that an artefact is built a single time and then promoted through staging to production. This guarantees the version your customers receive is the very same one that passed every test.
Rebuilding separately for each environment risks subtle differences creeping in, so a change might pass in staging yet fail in production. Building once removes that whole category of problem and makes releases far more predictable.
Frequently Asked Questions
How long do you keep old versions?
We retain enough history to roll back safely and to support audits, with a retention policy agreed to suit your needs.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.