-
New Feature
-
Resolution: Duplicate
-
Minor
-
None
It would be convenient if there was a pipeline step that would exit the run immediately, but not have it be necessarily be a failure.
This would be useful in situations where a run determines it no longer has work to do, and so it should end immediately as success (or whatever the current result state is).
If we have multiple such decision points in a build, doing this with conditionals gets incredibly messy quite quickly.
- duplicates
-
-
- Reopened
-
- links to
[JENKINS-41197] [Pipeline] Pipeline step to exit the build immediately as a success
Sean Sutherland
added a comment - jglickreturn only gets out of the current closure, unless you meant I have to be outside of any pipeline step block
node {
withEnv(["a=b"]) {
return
}
println "endenv"
}
println "endnode"
this will print out both "endenv" and "endnode"
Sean Sutherland
added a comment - jglick return only gets out of the current closure, unless you meant I have to be outside of any pipeline step block
node {
withEnv([ "a=b" ]) {
return
}
println "endenv"
}
println "endnode"
this will print out both "endenv" and "endnode" 
J Knurek
added a comment - Yeah, in general you may need to throw and catch something.
But that's exactly the point of this feature request:
If we have multiple such decision points in a build, doing this with conditionals gets incredibly messy quite quickly.
I don't think this is resolved, we only have workarounds until this feature is created.
I don't know how the error step is implemented, but it might be nice to change it to an exit step in which the error code can be added/removed as an option
J Knurek
added a comment - jglick
Yeah, in general you may need to throw and catch something.
But that's exactly the point of this feature request:
If we have multiple such decision points in a build, doing this with conditionals gets incredibly messy quite quickly.
I don't think this is resolved, we only have workarounds until this feature is created.
I don't know how the error step is implemented, but it might be nice to change it to an exit step in which the error code can be added/removed as an option I don't think this is resolved, we only have workarounds
That is why it is resolved as a duplicate.
For now, assuming you are inside the main script body:
return