Software has changed the world faster than almost any other industrial innovation and it’s only picking up speed. Companies are moving from infrequent, large code deployments to frequent, small and agile deployments. This trend is having a huge impact on the current software development processes. For example, in one of our most recent customer surveys, more than 65% of software teams noted that they are practicing some form of continuous delivery. It’s becoming the norm for software teams.

But implementing continuous delivery is not easy. Setting up build agents is complicated. Developers have to constantly juggle between different tools. And most of the time, the build is sitting in a queue, or you’re burying yourself in log files digging for information about failures.

Bitbucket Pipelines
That is until now. Bitbucket Cloud is introducing Pipelines to let your team build, test, and deploy from Bitbucket. It is built right within Bitbucket, giving you end-to-end visibility from coding to deployment. With Bitbucket Pipelines there’s no CI server to setup, user management to configure, or repositories to synchronize. Just enable it in one click and you’re ready to go.

It’s all Bitbucket – Manage your entire development workflow within Bitbucket. No need for a separate tool.

Instant setup – You can create and run your CD pipeline once you sign up for Bitbucket. No agent configuration required.

Fast feedback – We show build statuses automatically everywhere you care about them – on branches, commits and pull requests.

Pipelines is also a great fit for branching workflows like git-flow. Anyone on your team can adapt the build configuration to map the structure of your branches. Here is a quick look at some of the salient features of Bitbucket Pipelines:

Bring your own services to Bitbucket Pipelines
We worked very closely with some of the leaders in the industry so you can bring your own services to Bitbucket Pipelines, right out of the box. Whether you want to deploy, test, monitor code quality, or store artifacts, complete any workflow with the tool of your choice: Amazon Web Services, Ansible, bitHound, BrowserStack, buddybuild, Code Climate, JFrog, Microsoft Azure, npm, SauceLabs, Sentry, Sonatype, and TestFairy.

“Pipelines provided us with the perfect opportunity to bring the power of automated code quality analysis to Bitbucket users. We’re excited about the awesome potential of Pipelines and they’re only just getting started!” –Michael Bernstein, VP of Community, Code Climate.

Continuous Delivery options from Atlassian
We believe that the best way to provide our customers with a top-notch cloud CD solution is to build the service natively within Bitbucket Cloud. That’s why we built Bitbucket Pipelines and also why today, we’re announcing the end-of-life for Bamboo Cloud, which will be discontinued starting Jan 31, 2017. While Bamboo Cloud has helped many customers to adopt CD, we realized that we would not be able to deliver the experience and the quality of service that our customers need. If you’re a Bamboo Cloud customer, click here to learn more about the migration options.

If you want to build and ship behind the firewall, we’re still heavily investing in Bamboo Server as an on-prem CD solution.

Get early access to Bitbucket Pipelines
With Bitbucket Pipelines we want to empower every team to accelerate their releases. No more time wasted on setup and maintenance, just focus on the work you love. You can sign up for the Bitbucket Pipelines beta program today and request early access.

12 Comments

Nice :).
Will it be available for Bitbucket Server? Are there any plans to apply some of this functionalities for Bamboo and Bitbucket Server? Especially the plan configuration from within the repository?

We don’t have plans to support Pipelines in Bitbucket Server as Bamboo Server integrates really well with it already. We will keep on extending Bamboo Server and we’ve made some great improvements in the past releases around scale – plan configuration is something that has been on the radar but it’s too early to talk about commitments.

We don’t have plans to support Pipelines in Bitbucket Server as Bamboo Server integrates really well with it already. We will keep on extending Bamboo Server and we’ve made some great improvements in the past releases around scale – plan configuration is something that has been on the radar but it’s too early to talk about commitments.

Great job getting this functionality into bitbucket to react to github/travis!! Yay! 🙂
Can you please bring this functionality to Bamboo!?!? It would really help that product to stay competitive and for my developers to not move away from it. Build config as code is now the defacto standard.
This should be a top 5 feature on Bamboo’s backlog imo.

We’re running the pipelines in Docker so we do not have direct support for Windows yet. Regarding AppVeyor we do not have a direct integration with them but it should be possible to trigger a build in AppVeyor using their API (https://www.appveyor.com/docs/api/projects-builds).

We’re running the pipelines in Docker so we do not have direct support for Windows yet. Regarding AppVeyor we do not have a direct integration with them but it should be possible to trigger a build in AppVeyor using their API (https://www.appveyor.com/docs/api/projects-builds).

Excellent going guys. I am going to try this out today! I am currently deploying my saas product ClockIt https://clockit.io using Jenkins and Stash. Now this is truly innovative. Bringing everything under one platform. Sweet!! Maybe there is a better way to deploy our time and attendance software finally!!