I don't mean the after-script, the challenge is the step that hosts the after-script don't even get executed.
Consider this pseudo pipeline yaml:
definitions:
- step: &step1-will-pass
script:
- step1 script here
- step: &step2-will-fail
script:
- step2 script here
- step: ¬ify-build-status
after-script:
- notification script here
pipelines:
custom:
'release':
- step: *step1-will-pass
- step: *step2-will-fail
- step: *notify-build-status
In the custom pipeline 'release', when step2-will-fail gets executed and failed, the pipeline stops right there, The notify-build-status step will not be executed.
Hi @Xinyu Wang ,
Can't you move the notification to step-2?
There is a discussion for a similar problem and two related feature requests here and here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.