I forgot to mention, that having that I am able to reboot '"driven" machine
before actual build. "driver" starts a reboot of "driven" and waits, until
it is completed.
Am Montag, 22. Juli 2013 16:06:28 UTC+2 schrieb Olexij Tkatchenko:
>
> It worked, thanks! I have 2 nodes - node1 ("driver"), and
It worked, thanks! I have 2 nodes - node1 ("driver"), and node12
("driven"). "Driver" executes a downstream project on a node named
${NODE_NAME}2, which is obviously "driven". One can also go further and
"tie" node12 to downstream project by setting "*Leave this machine for tied
jobs only"*
Am
The combination Parameterized Trigger plugin + NodeLabel Parameter plugin might
work. The environment variable 'NODE_NAME' stores the name of the node.
On 21.07.2013, at 04:59, Olexij Tkatchenko
wrote:
> How to implement a dynamic selection of a node for downstream project based
> on name of
How to implement a dynamic selection of a node for downstream project based
on name of the node of upstream project? For example, if the node for the
upstream project is called "node1" then the node for the downstream project
should be called "node11", for "node2" - "node21" and so on.
--
You
