-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: build-flow-plugin
-
Labels:None
-
Environment:java.runtime.version 1.6.0_26-b03
os.name Windows 7
os.arch x86
Jenkins 1.467 (but tried version before that as well)
-
Similar Issues:
Setting up a Build Flow project with the following configuration (tried maybe different combinations of white space/newlines
parallel (
,
{ build("Master Wayfinder Flex") })
build("Master - Wayfinder Archive")
When the build starts I get this in the console...
parallel {
}
Trigger job Master - Wayfinder Archive
So it triggers the last build but doesn't trigger the builds before it.
I am using 1.471 with plugin 0.3. I have configured 9 parameterized jobs (defaults set). with anonymous access, it works properly with default parameter values. If I migrate plugin to 0.4 it fails as it can't use default parameter..
Is this plugin supposed to handle parameters? I mean If I make this job parameterized, and set up following way
parallel (
{ build ( "job1" , p1: "${p1}", p2: "${p2}", p3: "${p3}" ) },
{ build ( "job2" , p1: "${p1}", p2: "${p2}", p3: "${p3}" ) }
)
should it work?
Thanks
S
I use different parameters in build. It works. The only problem was (in 0.3 version) to get it from parameters of flow. As far as I can see in discussion of plugin (see comments in wiki for Build+Flow+Plugin) the following sting should work in 0.4 version:
build("paramJob1", PARAM_1:params["BUILD_PARAM"])
Enabling "read job" permissions for Anonymous worked around this for me too.
Code changed in jenkins
User: Nicolas De Loof
Path:
src/main/groovy/com/cloudbees/plugins/flow/FlowDSL.groovy
http://jenkins-ci.org/commit/build-flow-plugin/ef1dab2cdc87fc021b97a8aae758a3c1ba9ee312
Log:
[FIXED JENKINS-14027]
I have arrows from a circle to executed jobs (Jenkins 1.472, build-flow 0.4), so it is looks like a bug of your configuration or limitation of current plugin (see #13520 part 2).