Bitbucket Pipes launched in February to help teams adopt DevOps practices by simplifying the configuration and maintainence their CI/CD pipelines. Pipes are updated and maintained by the author meaning teams never have to worry about updating or re-configuring them, and making the set up of external services across pipelines and repositories a breeze.
We've seen great adoption and use of pipes since launch, and below is a recap of some of the newer and most popular pipes teams are using to help automate their CI/CD pipelines.
With pipes available for a multitude of use cases including deployment, workflow automation, artifact management, and more, it's easy to utilize supported pipes to configure your pipeline to your exact needs.
- AWS S3 Deploy: Deploy your static website to Amazon S3. You can easily use Bitbucket Pipelines to deploy your personal or company website on AWS.
- SonarCloud Scan: Scan your code with SonarCloud to detect bugs, vulnerabilities and code smells in more than 25 programming languages.
- Slack Notify: Sends a custom notification to Slack. With the available Bitbucket Slack integration you get notifications on standard events, such as build failures and deployments. Use this pipe to send your own additional notifications at any point in your pipeline.
- AWS CloudFormation: Provision and manage all your cloud infrastructure resources using AWS CloudFormation. This pipe lets you easily practice one of the key elements in DevOps: Infrastructure as Code (IaC) – all you need to do is to write and store the infrastructure templates in your Bitbucket repository and configure the pipe to apply the changes as a part of your CI/CD pipeline.
- Heroku Deploy: The pipe will deploy your application using Heroku's Platform API and will authenticate requests using the provided token.
- Firebase Deploy – Deploy your code to Firebase. This pipe deploys code and assets from your project directory to your Firebase project.
Since launch we've almost doubled the number of supported pipes available to use as well. These include but aren't limited to:
- Jira transition
- Pagerduty create incident
- Email notify
- Bitbucket trigger pipeline
- FTP deploy
- AWS Cloudfront invalidate
- Serverless deploy
- Debricked scan
- Cloudsmith publish
- SonarCloud quality gate
- Beagle security test
- SSH run
- AWS ECS deploy
- AWS ECR push image
See the full list of pipes here.
Create your own custom pipes
And while we're constantly adding to our directory of supported pipes, we also know that teams not only have different tools they like to use, they also have different ways of working. In order to give these teams the flexibility to work the way they want with ease, we made it possible to create custom pipes to use as part of your CI/CD pipeline!
It's simple to get started, with some examples of custom pipes built here, here and here. And stay tuned over the coming days for an opportunity to share the custom pipes you've written – we'll have some swag for a lucky few that do!