Command steps has a
soft_fail attribute, which allows the build to not fail if the command is not successful. I’d like a similar option for trigger steps: An option that allows the build to not be considered a failure even if a certain trigger step fails.
We are already using
allow_dependency_failures to allow other steps in the pipeline to run even when the trigger fails; however, a failure in the trigger step still causes the overall build to be considered a failure, which, in our case, makes it more difficult to visualize whether the failures for that pipeline were actual failures, versus only failures in the steps that we consider soft failures.
Hi @martani-benchling ,
Thanks for raising this.
I can see the value in adding this as an option to the trigger step! I’ve sent this over to the product team as a feature request.
Seconding this feature request, we like to trigger some builds which we want to allow soft fail, but do not want to fully ignore like by running async, any update on this?
Unfortunately no update yet. The team is aware of the request but hasn’t got to deciding and prioritising on it yet
I am also looking for this feature on the trigger step. We want to wait on the triggered step to complete, but we don’t want the build to be considered ‘failed’ if the triggered build fails.
Hey! Unfortunately, we haven’t had the capacity to look at this properly yet, but it’s in our backlog. We’ll update you when there is more news.