A deployment is a change, whether or not it is recorded as one.
Bitbucket Pipelines runs builds and deployments from the repository, inside the Atlassian estate rather than on separate infrastructure with separate credentials. Our work is migration from external build tooling and connecting deployments to change control.
Pipelines runs builds and deployments inside the same estate as the work and the approvals. We migrate from external build tooling and connect what ships to the record that authorized it.
What it is
Bitbucket Pipelines runs builds and deployments from the repository, inside the Atlassian estate rather than on separate infrastructure with separate credentials.
It is for organizations moving off self-managed build tooling, particularly where the existing system holds credentials nobody has reviewed in years.
What it does
Builds inside the estate
No separate build server to patch, and no separate credential store to forget about.
Deployments that can be recorded
What shipped can be linked to the change that authorized it, if the change model exists.
Where it fits
L2, platform and migration, reaching up into L3. A deployment pipeline is a change mechanism, and it usually holds the most privileged credentials in the estate. Whether that is governed is a change control question, not a build one.
What we do with it
Migration from self-managed build tooling
Moving pipelines off infrastructure you maintain, with the credentials inventoried rather than copied.
Deployment credentials as identities
Build credentials are non-human identities with wide scope, and they belong in the same review as every other one.
Connecting deployment to change
Where a release requires approval, the pipeline and the change record have to reference each other.
Where it earns its place
An organization retiring a self-managed build server
The migration is straightforward. The credential inventory it forces is the valuable part.
A regulated environment that has to evidence releases
Linking a deployment to an approved change is the difference between a report and a reconstruction.
Proof
World Class Software Development Finalist, 2024-2025
Atlassian Partner Awards, 2024-2025
Questions we get
Can we migrate incrementally?
What about our existing build scripts?
Licensing
Build minutes are consumed capacity rather than seats, which makes them one of the easier things to over-provision quietly. That reconciliation sits with the rest of the estate in licensing and renewals.
Atlas Bench delivered a maintainable CI platform solution that transformed how we build, test, and release products. They identified roadblocks early and delivered on time. Highly recommend for any DevOps project.
Paul Mohan Das
Engineering Manager