Well, I don’t know how it chooses but I would not be surprised if there were no
jobs running, that it would choose the same one first each time.
BTW, if your first build chooses one slave from a labeled group, you want to
pass on to the next job the specific slave chosen. For example, you don’t care
which Windows build machine the first job ends up on, but you want the other to
follow suit.
def nodename=build.getBuiltOnStr()
out.println "This node is " + nodename
b = build ("second-job-core-builder",
BUILD_NODE:nodename)
Because what you want is the 2nd job to run an the specific slave that the
first job selected. If you follow me?
From: [email protected]
[mailto:[email protected]] On Behalf Of Katie Outram
Sent: Tuesday, March 03, 2015 2:32 PM
To: [email protected]
Subject: Re: Build Flow Plugin with Node Label Parameter Plugin
Thanks for this information! This is now farther along and my entire job is
building on one slave (not on both).
I do have one other strange thing happening now.
I have two slaves configured in the node label parameter plugin, however
everything is only executing on one slave, no mater how many builds I have
running. Do you have any idea as to why that is happening?
On Tuesday, March 3, 2015 at 10:47:03 AM UTC-5, rginga wrote:
I have had good success doing this but I pass the NODE_NAME as a specific
parameter:
Build (“AnyBuild”,
BUILD_NODE:”BUILDHERE”)
Where BUILD_NODE is a NODE parameter
From: [email protected]<javascript:>
[mailto:[email protected]<javascript:>] On Behalf Of Katie Outram
Sent: Tuesday, March 03, 2015 10:41 AM
To: [email protected]<javascript:>
Subject: Build Flow Plugin with Node Label Parameter Plugin
Has anyone had success using the Build Flow Plugin with the Node Label
Parameter Plugin?
Right now I have a build flow that executes some of the steps on Machine A and
other steps on Machine B, eventhough I am passing the NODE_NAME and NODE_LABELS
to the children jobs via an Environment Variable file.
If you have done this, do you have any suggestions on how to make certain all
of the builds that are part of the flow operate on either Machine A or Machine
B and not both?
--
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]<javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/38fbb947-a6d2-494f-b2dd-7cad9e76a7db%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/38fbb947-a6d2-494f-b2dd-7cad9e76a7db%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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]<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/290c1f31-c24b-4e5d-99a1-ebd81bb2f7f2%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/290c1f31-c24b-4e5d-99a1-ebd81bb2f7f2%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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/6C6EE445A6F6CE4E8A0FFB51B071A4E26E505EBD%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.
