Currently, it’s possible to add a step that is run if the build fails (using is_always_run: true).
If the build is aborted though, no steps from that point onwards will run.
We would like to be able to create a step that will be always run, even if build gets aborted, i.e. to perform a necessary cleanup of external services.
Build may be aborted among others due to elapsed build time or lost connection to build VM. So even if such flag is added it may not be possible to run anything from inside affected workflow in some cases.
To achieve such result you can e.g. use Bitrise Start Build step and perform cleanup from parent workflow.
Using Bitrise Start Build will use up another concurrency. Ideally we want to be able to run clean up steps after build is aborted. Doesn’t matter if build can be aborted due to elapsed build time/lost connection but 90 percent of the time, aborted builds due to rolling build cancellation or manual trigger, we want to be able to clean up/report build status back to git provider.
We too wanted such a capability to run a step if build is aborted.
Having a way to run cleanup steps for a job that gets aborted should be a fundamental feature of any CI orchestration solution. Definitely expected from a paid solution like Bitrise