Is there a way to define a step that is allowed to fail? It would come in handy to run certain sanity checks, like linting or static code analysis.
It’s important to create visibility on these steps, but they are not necessarily blocking.
I know there is the continue_on_failure on wait steps, but it will not work for this use case for example:
- command: "lint.sh" - wait: ~ continue_on_failure: true - command: "echo Building code" - wait - command: "echo Deploying code"
If the linting failed the deployment will never happen, even if the failure wasn’t exactly blocking.