CI/CD tools are an integral part of a software team’s development cycle. Whether you’re using it to automate tests, a release process, or deployments to customers, all teams can benefit by incorporating CI/CD into their workflow.
Want to know the different between continuous integration, continuous delivery, and continuous deployment? Check out our CI/CD microsite for articles, guides, and more.
Bitbucket Pipelines is CI/CD for Bitbucket Cloud that’s integrated in the UI and sits alongside your repositories, making it easy for teams to get up and running building, testing, and deploying their code. Teams new to CI/CD all the way through to those with sophisticated delivery and deployment pipelines
Teams new to CI/CD or familiar with setting up their own CI servers will appreciate how easy it is to get started with Pipelines. It’s a 2-step process to configure a pipeline and there’s a number of templates for languages available to get started. And because Pipelines is a cloud-native CI/CD tool you never have to worry about provisioning or managing physical infrastructure, meaning more time focusing on other priorities.
We know every team has a different way of working and this extends to the tools they use in their workflow. With Pipes it’s easy to connect your CI/CD pipeline in Bitbucket with any of the tools you use to test, scan, and deploy in a plug and play fashion. They’re supported by the vendor which means you don’t need to manage or configure them and, best of all, it’s easy to write your own pipes that connects your preferred tools to your workflow.
There are currently over 60 pipes offered by leading vendors such as AWS, Microsoft, Slack, and more. Learn more about our integrations and get started.
For those looking to implement a more mature CI/CD workflow that involves a release process or deployment to environments, Pipelines offers a robust set of deployment functionality that provides teams the confidence and flexibility to track your code from development through code review, build, test, and deployment all the way to production. For more sophisticated workflows you can create up to 10 environments to deploy to, and see what code is being deployed where via the deployment dashboard.
Increased visibility and collaboration
Visibility into what’s going on and what’s been deployed to customers is vital to all teams. Pipelines has integrations with tools like Jira, Slack, and Microsoft Teams that provides context on your builds and deployments right where your team plans and collaborates. For collaboration tools like Slack it’s easy to see what’s happening with your CI/CD tool and act on it too.
When integrated with Jira Software, Pipelines provides visibility for everyone who works inside Jira from backlog all the way through to deployment, surfacing deployment and build status in Jira issues as well as which environments a Jira issue has been deployed to as well.
Pipelines pricing is based off a simple, consumption-based model of build minutes used, and every Bitbucket plan includes build minutes. Unlike other cloud vendors we don’t charge for concurrency, meaning you don't pay extra to follow CI/CD best practice and run your pipelines steps as fast as you can.
|Plan type||Build minutes per month|
If you’re wondering where your team might stand when it comes to build minutes usage, we typically see small teams with fast builds using about 200-600 minutes. Head here to learn more about build minutes and how they work.
Get started with CI/CD today
Every team should have a CI/CD tool as part of their development toolchain, whether you’re simply interested in automated testing or looking to create sophisticated deployment workflows.
Whatever your requirements may be, a tool like Pipelines is perfect for your needs and it’s free to get started!
For a step-by-step tutorial of how to set up Pipelines for your team, head on over here.