-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins: 1.612
Workflow (all): 1.10-beta-1
Workflow multibranch: 1.9-beta-2
Steps to reproduce:
1. Create a multi-branch workflow project
2. Select a git repository as a branch source
3. Set property strategy to "named branches get different properties"
4. Add a parameter property (as the default or as an exception that matches the branch you're building. both seem to not work) of a string or boolean with a set default value
5. Run a branch that attempts to use that property
6. Property does not appear to be accessible from Jenkinsfile
Example
Set parameter property of 'test_parameter' with a default value
Attempt to use the parameter
def param = test_parameter
node("nodejs && swarm") {
checkout scm
println(param)
...
this exception gets thrown when the script is being executed.
groovy.lang.MissingPropertyException: No such property: test_parameter for class: groovy.lang.Binding
I've tried accessing
- boolean and string parameters
- As properties of the 'env' object or directly (The current tutorial for the workflow-plugin suggests that parameters are exported as variables in the global scope)
And I can't seem to get it to work in any instance
- depends on
-
JENKINS-30519 Declarative job properties in multibranch
- Resolved
- is blocking
-
JENKINS-32396 Option to suppress automatic SCM trigger
- Resolved
- is duplicated by
-
JENKINS-30492 Already created sub jobs for Multibranch Workflow are not updated when configuration is changed
- Resolved
-
JENKINS-34304 jenkins.branch.Branch is not updated on child projects when corresponding jenkins.branch.BranchSource configuration is changed
- Closed
-
JENKINS-33125 "add property" button broken in property strategy
- Closed
- links to