I have a build flow plugin configuration for my build job in
jenkins(main-build-job). I want to make sure that my build occurs on
one of two machines so I installed the nodelabel parameter plugin. My
build flow is
build ("joba.sh", PARENT_BUILD_ID :
build.properties.environment['BUILD_ID'])
parallel (
{
build ("jobb.sh", EnvVarFile :
bParent.build.properties.environment['ENV_VAR_FILE'])
},
{
build ("jobc.sh", EnvVarFile :
bParent.build.properties.environment['ENV_VAR_FILE'])
},
{
build ("jobd.sh", EnvVarFile :
bParent.build.properties.environment['ENV_VAR_FILE'])a
}
)
My NodeParameter plugin is set on the main job (main-build-job) that
executes the steps above with configuration settings of
default node: MachineA, MachineB
possible node: MachineA, MachineB
Allow multi node selection for concurrent builds
Ignore offline nodes
When my main job (main-build-job) executes(the job that calls the build
flow), it runs on Machine A. My next job (joba.sh) is executing on a
totally different node (Machine X). I stop both jobs that are running at
that point.
I'm guessing I have missed a configuration setting somewhere or I've missed
something in my understanding of this plugin. Can anyone point me in
the right direction to so that all of my jobs (main-build-job, joba, jobb,
jobc, jobd) all execute on the same node?
Thanks!
"Execute concurrent builds" and "Allow multi node selection for concurrent
builds" only make sense together!
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/af11dc35-4104-4cd4-b44c-5c44013e110e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
