Bitbucket Pipelines
Why Jenkins might cost you 10x more than Bitbucket Pipelines
And slowing down your developers and your pace of innovation in the process Any company still running their own CI/CD, such as Jenkins, is paying a price. The question is which one: Each of these is extremely costly, and yet many software teams still host and run their own CI/CD for two reasons: tools like […]
Unlocking insights: Introducing Step Metrics for Bitbucket Pipelines
We’re excited to announce step metrics – a new capability coming to Bitbucket Pipelines to help you better manage and optimise your CI/CD workflows. Ever wondered what’s happening under the hood during your pipeline runs? Step metrics provide a window into the resource usage of your build and service containers. More specifically, step metrics let […]
Introducing parent/child pipelines
We’re excited to announce the launch of parent/child pipelines for Bitbucket Pipelines. This powerful new capability lets you define a step within a pipeline that triggers and encapsulates a whole other pipeline, which can help to streamline more complex workflows into modular pieces and achieve greater parallelism within your pipeline. As teams and codebases grow, […]
Evolving deployments in Bitbucket Pipelines: Concurrency Groups and Environments
We’re excited to announce that Bitbucket Cloud is introducing two powerful new features in Bitbucket Pipelines: Concurrency Groups and Environments. These enhancements are part of a broader initiative to make the Deployments functionality more flexible and user-friendly by breaking down its current monolithic structure into smaller, more granular capabilities that you can control directly. Background […]
Enhancements to Bitbucket Pipelines step conditions
Not every file change in our repository requires running a pipeline. For changes to files, such as README, .gitignore, and CODEOWNERS, you may not want to run 30-minute browser tests or full deployment pipelines. To allow you to skip steps for low-impact file changes and eventually make your pipelines run faster, we are introducing a […]
Introducing Runtime v3 – Multi-arch images and more control over Docker
Historically, when using the Pipelines Docker service, the step would automatically have the Docker CLI executable mounted into the build container. While this approach was initially convenient and helped onboard new customers, it limited flexibility in several areas. For example, customers couldn’t easily use the latest docker buildx features because the CLI version was pinned. […]
Use variables in any part of your Pipelines .yaml
In the past, variables in Bitbucket Pipelines were scoped to only operate within script sections of a Pipelines workflow. This limited their usefulness and restricted users from being able to fully parameterize their workflows. Today we are releasing an enhancement that will allow variables to be used within any section of a Pipelines .yaml file, […]
Introducing the “retry” step failure strategy for Bitbucket Pipelines
Overview Recently we introduced support for Failure Strategies, which allows developers to implement more powerful logic and control flow into their workflows. Today, we are excited to announce a new step failure strategy, retry, which can auto-retry your failed steps without requiring any input from the user. No matter what happens to your step, whether […]
Easily share data between steps in Bitbucket Pipelines
We’re excited to announce the release of a new feature in Bitbucket Pipelines designed to make it easier for you to share variables between steps within your workflows. Overview This feature allows you to define environment variables in one step and make them accessible in subsequent steps within the same pipeline. Previously, sharing variables between […]
Announcing ARM builds in cloud for Bitbucket Pipelines
We are excited to announce the release of ARM builds in the Pipelines cloud runtime. Our release of Linux based ARM runners in cloud allows you to build and deploy software for ARM-based systems with all the benefits of our fully managed CI/CD platform. To use the new cloud ARM runners in your pipeline, make […]
Introducing step failure strategies in Bitbucket Pipelines
We are excited to introduce a new capability in Bitbucket Pipelines – Step Failure Strategies. This is the first of a set of new features allowing developers to implement more comprehensive logic and control-flow inside their CI/CD pipelines. Failure Strategies are designed to give you explicit control over how your pipeline behaves in the event […]
Upcoming Changes to Pipelines Log Retention Policy
Bitbucket Pipelines is making changes to the way we manage build logs to create a more predictable and standardised set of policies for managing customer generated data. As part of these changes, we’re standardising and clarifying our log retention policies to ensure they are clear to customers and aligned with industry standards. What’s changing? Starting […]
Bitbucket Pipelines and OpenID Connect: No more secret management
Bitbucket Pipelines now allows you to talk to your favorite third-party applications without an access token or secret. You no longer need to store your secrets in Bitbucket Pipelines. You can generate an OpenID Connect token in Bitbucket Pipelines, and use that to talk to any third-party application that supports OpenID Connect. Why use OpenID […]
Bitbucket Pipelines now supports building Docker images, and service containers for database testing
Companies love delivering their applications using Docker. According to Forrester, 30% of enterprise developers are actively exploring containers, and Docker is the dominant DevOps tool, with 35% of organizations adopting it, according to a recent RightScale survey. Docker provides a painless method of building and deploying applications as a set of independent micro services, which are scalable and resilient. […]
3 steps to enable Bitbucket Pipelines build notifications in Hipchat
Every time you trigger a build in Bitbucket Pipelines, whether by pushing commits or creating a pull request, you have to remain at your desk refreshing email to see if the build has passed. All to avoid wearing the cone of shame for not finding out about a failed build quickly. Wouldn’t it just be […]