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.