Is there a way to define a set of commands to run when a pipeline fails? Edited

I'm running unit tests via Pipelines, and would like to be able to persist the detailed results generated by the tests (e.g. failure traces, timing, etc.). I've seen the deployment guides page, but it seems to only cover build artifacts, not test results.

If I add an "upload results to GCS" command after the "run tests" command it only runs (understandably) if the tests pass.

Is there any sort of post-step hook where we can specify commands that should run every time? Or an on-failure hook for commands that run when the build fails?

Or, more generally, if there's a way to get build artifacts out of the pipeline even if a step of the pipline fails, that would work too.

1 answer

0 vote

Hi Michael, 

we currently don't have support for such 'final' tasks unfortunately. 

We do have an open feature request for this, that you can vote on and track:

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,022 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you