-
Improvement
-
Resolution: Fixed
-
Minor
-
-
workflow-support 2.22
Pipeline currentBuild should expose the build causes.
Currently, users have to resort to rawBuild to get this information
http://stackoverflow.com/questions/33587927/how-to-get-cause-in-workflow
- is blocking
-
JENKINS-53193 Provide currentBuild.isRestartedRun and .isRestartedStage global variables
-
- Open
-
- is duplicated by
-
JENKINS-54227 Safely expose the Cause(s) associated with the current build
-
- Resolved
-
-
JENKINS-55758 Add Whitelisted method to get the trigger cause
-
- Resolved
-
- is related to
-
JENKINS-43754 Global pipeline library & simple 'checkout scm' rebuilds each polling cycle
-
- Open
-
- relates to
-
JENKINS-31576 Sandboxed access to upstream build information
-
- Resolved
-
-
JENKINS-37366 Pipeline "currentBuild" should expose project name
-
- Resolved
-
-
JENKINS-54323 Create a Pipeline step to set the current build's display name, description, etc.
-
- Open
-
- links to
[JENKINS-41272] Pipeline "currentBuild" should expose build causes
Link |
New:
This issue relates to |
Link |
New:
This issue relates to |
Component/s | Original: pipeline [ 21692 ] |
Labels | New: cloudbees-internal-pipeline |
Remote Link | New: This issue links to "CloudBees Internal CD-124 (Web Link)" [ 18962 ] |
Remote Link | New: This issue links to "CloudBees Internal CD-177 (Web Link)" [ 19111 ] |
Assignee | New: Sam Van Oort [ svanoort ] |
Remote Link | New: This issue links to "workflow-basic-steps 71 (Web Link)" [ 21831 ] |
Assignee | Original: Sam Van Oort [ svanoort ] | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |