-
New Feature
-
Resolution: Unresolved
-
Minor
-
-
Pipeline - April 2018
The error step results in a workflow with a "FAILURE" state.
It is desirable to be able to end a workflow early from within the workflow itself but not have the workflow in an error state (which would imply a user needs to take a look at why it failed and perform so work).
e.g.
say I do not want to deploy any code to production on a Friday afternoon
A step that stops the workflow on a Friday afternoon should not result in the build being failed but in one that it has been intentionally cut short.
- depends on
-
JENKINS-34464 DescribableModel can't inspect ReverseBuildTrigger; need binding for Result
- Resolved
- duplicates
-
JENKINS-45579 Step to set stage or parallel status
- Resolved
- is duplicated by
-
JENKINS-41197 [Pipeline] Pipeline step to exit the build immediately as a success
- Resolved
-
JENKINS-40483 Jenkinsfile able to stop current job
- Resolved
- is related to
-
JENKINS-39203 All stages show up as UNSTABLE when only one stage should
- Resolved
-
JENKINS-49073 build job propagate true propagates FAIL when state is UNSTABLE
- Resolved
-
JENKINS-30412 Access to build's own changelog from script
- Resolved
- relates to
-
JENKINS-35988 Equivalent to polling commit exclusions for branch indexing
- Resolved
-
JENKINS-41943 DP should have an easy way to say don't run subsequent steps if result is set.
- Closed