Filter nodes with propagate: false when evaluating WarningActions #598
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WarningAction
tobuild
nodes to allow pipeline visualizers (blueocean, pipeline graph view, etc.) to show the result of downstream builds even if ignored bypropagate: false
. See https://issues.jenkins.io/browse/JENKINS-70623.post
condition sections for declarative pipelines which are using the presence ofWarningAction
s in order to determine which post conditions to evaluate.propagete: false
in itsArgumentsAction
.WanringAction
s whenpropagate: false
.