Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
Description
See PR 198 for details. Intuitively you would expect the scm global variable to be defined in all loaded code, but it is only available from the main script, and there is no straightforward way for other CpsScript instances to get it.
Need to find a way to make global variables reliably be accessible from all script files loaded in a flow build. Current idea is to save them in CpsThreadGroup.
Attachments
Issue Links
- is related to
-
JENKINS-30414 RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject getProperty java.lang.String (org.jenkinsci.plugins.workflow.cps.CpsClosure2.docker)
-
- Resolved
-
-
JENKINS-30531 Define SCMRevisionAction from SCMBinder
-
- 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