Pipelines executions can contain
after-steps. Steps that are executed after a pipeline run has either failed or passed. A good use-case for
after-steps are notifications to an IRC channel or HipChat Room, closing an issue on a project management system or sending out a newsletter after a successful deploy.
Here’s an example that leverages the hipchat-notify step to send a notification. Note the use of the
after-steps element to signify that the message has to be sent after the steps of the deploy.
deploy: steps: - script: name: fabric deploy code: | fab deploy after-steps: - hipchat-notify: token: $HIPCHAT_TOKEN room_id: id from-name: name
One major difference between steps and after steps is that failing after-steps do not change the result of the pipeline run.