Allow a step to fail and not mark the deploy as failed
For steps like 'post to a slack room' or 'update the build server with a token', I think it is reasonable to provide some sort of toggle to allow the step to fail without failing the entire deploy.
I agree this is a good idea. If I update status.io at the end of my deployment with a deploy success\fail and the call to status.io fails, the deployment is considered to be a failure. However, failing to update the status.io page at the end shouldn't mark the whole deployment as a failure.
I also really need this feature.
I have a specific step at the end of the process which runs the selenium integration tests.
This is more like an "informational" step as I still need the deployment to be marked as success either if the tests failed or not (or you could create a "warning" deployment status in yellow)
This deployment warning status would allow me to decide wether to deploy or not to the next environment after checking these warnings.
Thank you for this amazing tool
Paul Milbank commented
It doesn't mean the deploy has failed, but it is still marked in the UI as a failed deploy. If there was a way to differentiate a step as fail with warning or fail with error, the UI could reflect that. Maybe if a step fails with a warning, the UI could show a tick still, but in an orange box instead of a green one. If a step is very important, it could be set to fail with error and the deployment is shown as failed like it is currently.
Alexander Sidorenko commented
Some steps, like notifications to Slack, may fail, but this doesn't mean, that deploy has failed.
Need ability to not fail the deployment if one of the steps (such as email notification) fails.