Teams are deploying code faster than ever, thanks to continuous delivery practices and tools like Bitbucket Pipelines. But this has caused a huge problem: it’s hard keeping up with all the deployments and knowing where things are at.
In teams adopting continuous delivery, you hear questions like:
- What changes were deployed to production yesterday?
- Can I try out this feature in the test environment?
- Who broke the staging environment?
To help you answer these questions and more, we’re excited to announce Bitbucket Deployments in Bitbucket Cloud. Bitbucket Deployments is the first deployment solution that sits next to your source code and can be configured with a single line of code.
Now there’s no need to set up and maintain a separate deployment tool, or scroll through unrelated builds in your CI service to analyze deployments. Bitbucket can manage and track your code from development through code review, build, test, and deployment – all the way to production. (In the future, we’ll be adding integrations with Jira to keep your boards and issues in sync with deployments as well!)
Let’s jump into the specific features to show you how tracking deployments with Bitbucket can help your team move faster today.
Deployment visibility with the new dashboard
Our new Deployments dashboard gives you a single place to see which version of your software is running in each environment, and a complete history of earlier deployments.
Environments in Bitbucket are configured out of the box as test, staging, and production, and your team can choose to use one or more of these environments as needed. The current status shown on the dashboard reflects the last deployment that was attempted to that environment, as configured via the Pipelines YAML file.
Also shown on the dashboard is a full deployment history with a list of every deployment to each environment. You can see which build went out, who deployed it, and when it was deployed. When diagnosing problems, the history list can be filtered to show all the deployments to one environment to trace back and find the offending change.
Tying code and deployments together in the deployment summary
Bitbucket Cloud is now one tool to manage your source code and your deployments, so it’s smarter than the average deployment tool. You don’t have to wonder which code changes went out in a deployment, Bitbucket can tell you!
Here’s what you’ll see if you click on one of the deployments on the dashboard:
With this complete and detailed history of every deployment, investigating problems becomes much easier. Your team can quickly confirm the cause of a bug and roll forward with the fix.
Preview and promote deployments between environments
Preventing mistakes is a key part of every team’s deployment process. This is why so many teams still have manual checkpoints in an otherwise automated process. However, these manual checkpoints are more difficult than they need to be, with lead developers trawling through dozens of diffs and PRs to review a set of changes prior to pushing them live.
To help make this easier, Bitbucket Deployments will soon have a built-in promotion workflow, letting you take a verified build that is running in one environment and promote it to the next:
We’re also improving the chat notifications for Stride, HipChat, and Slack to keep your entire team in the loop about the releases once they go out. You’ll see Bitbucket Deployments round out with these improvements in the coming weeks.
Get started by enabling deployments in your build
Check out the example below, where tracking is enabled for test, staging and production deployments:
Please give it a try and let us know your thoughts.
Stay tuned for more on deployments…
Today we started with a quick introduction to the new Bitbucket Deployments. In the coming weeks, we’ll have a bunch more to share, covering CD best practices and the future of Bitbucket Deployments. Stay tuned!
Excited about this news? Tell us why on Hacker News or Reddit.
Bitbucket Pipelines Team