Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit25bcdf7

Browse files
Update hooks.md
Repeated warning about on_success, on_fail, and on_finish segments not affecting pipeline outcome at all (and pipeline continuing regardless) after feedback from an enterprise customer who had a team fail to read this warning and make a significantly expensive mistake
1 parentefea3ee commit25bcdf7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎_docs/codefresh-yaml/hooks.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -298,7 +298,7 @@ steps:
298298

299299
##Controlling errors inside pipeline/step hooks
300300

301-
By default if a step fails within a pipeline, the whole pipeline will stop and be marked as failed. This is also true for`on_elected` segments as well. If they fail, then the whole pipeline will fail (regardless of the position of the segment in a pipeline or step).
301+
By default if a step fails within a pipeline, the whole pipeline will stop and be marked as failed. This is also true for`on_elected` segments as well. If they fail, then the whole pipeline will fail (regardless of the position of the segment in a pipeline or step). However, this only applies to`on_elected` segments -`on_success`,`on_fail` and`on_finish` segments do not affect the pipeline outcome at all, and a pipeline will continue even if one of these segments fails.
302302

303303
For example the following pipeline will fail right away, because the pipeline hook fails at the beginning.
304304

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp