Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
SCMBinder currently uses some hacks to save an SCM object in the build. Perhaps it would be better to use SCMRevisionAction, which was intended for this purpose.
Attachments
Issue Links
- is related to
-
JENKINS-30222 Multibranch scm variable not accessible from non-main scripts
-
- Resolved
-
- links to
Code changed in jenkins
User: Jesse Glick
Path:
multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/SCMBinder.java
multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/SCMVar.java
multibranch/src/main/resources/org/jenkinsci/plugins/workflow/multibranch/SCMVar/help.jelly
multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/SCMBinderTest.java
http://jenkins-ci.org/commit/workflow-multibranch-plugin/d8d9403029143715efee336d7094d46cef758d6f
Log:
[FIXED JENKINS-30531] Set SCMRevisionAction when we do a build, so client code can get access to this record.
Has the happy side effect of fixing
JENKINS-30222: scm as a global variable can be used unqualified from library code.Originally-Committed-As: 4e9bd117797620e2f11c03f4053e8210d3086eac