New Feature: Step Failure Strategies

Hi all - We're excited to announce a new capability in Bitbucket Pipelines we're calling Step Failure Strategies.

Detailed information is available on our announcement blog: 

https://www.atlassian.com/blog/bitbucket/introducing-step-failure-strategies-in-bitbucket-pipelines

3 comments

Ivan Peevski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2025

Additional suggestions for strategies

- rerun on a different runner (4x, legacy, on-prem)

- rerun on a different docker image (fallback to an older runner)

- notify - same as ignore, but also send email/slack message to someone to highlight the issue

- custom action(s) - list of steps to be executed on failure (a bit like how `after-script` runs). The above (notify) can be done using this instead of it being its own strategy. This can also allow for reports to be added to the PR

Like # people like this
Jonathan Hein
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 20, 2025

An end early and mark pipeline complete (but not failed) option would be a nice Step Failure Strategy.

Example: When it's detected the test suite has run successfully previously for this changeset.

Michal Šimon
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 20, 2025

It would also be cool to set this on an external commit status via the API. SaaS Tools like static code analyzers can report back to Bitbucket in a more granular way and help control the flow.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events