Use Bitbucket Pipeline to test against next version of language to not fail but alert

Eric Poe_3bt31i

We currently have our pipeline run against one version of our programming language using our own Docker image. I would like, also, to test against the next version of the language so that we are alerted to BC breaks for potential fixing in the same PR or in a subsequent PR.

Is there a way to have one pipeline step stop on failure and another continue, perhaps with a warning, on failure?

Theodora Boudale

Hi Eric and welcome to the community!

We will be releasing a feature soon that will allow a pipeline to continue when a step fails. This is not available yet and there is no continue-on-error flag.

When this is released we will post an update in this feature request:

• https://jira.atlassian.com/browse/BCLOUD-21670

You can add yourself as a watcher (by selecting the link Start watching this issue in the feature request) if you'd like to get notified via email on any updates. We will most probably release a blog post about this as well, in https://www.atlassian.com/blog/bitbucket.

This is the latest update on the feature request from one of our product managers about what we are planning:

• https://jira.atlassian.com/browse/BCLOUD-21670?focusedId=3540376&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3540376

When this feature becomes available, I don't believe that we will be sending a notification for these failed steps. However you could make use of an after-script on that step that checks the step's exit code using the default variable $BITBUCKET_EXIT_CODE.

In the after-script, you could use a command like the following so that the after-script exits if the step is successful:

- if [ "$BITBUCKET_EXIT_CODE" == "0" ]; then exit 0 ; fi;

If the step fails, the after-script will continue. You could then use one of the available pipes to send e.g. an email notification or a Slack notification about the failure:

• https://bitbucket.org/product/features/pipelines/integrations?&search=notify

Again, all this info I shared is for when this feature becomes available.

Until this feature is released, the only way for the pipeline to continue with a failed step is by adding the command set +e in the beginning of a pipelines step in your yml file. Please keep in mind that if you do this the step will show as successful even on failure, and the only way of figuring out if a command failed would be by examining the output of each command in the build log.

Please feel free to let me know if you have any questions!

Kind regards,
Theodora