Before the reboot, you could queue up the job you want to run right
after reboot. If other jobs may be competing, you can give your special
job a higher priority (priority sorter plugin).
Eric
On 3/11/2016 7:05 AM, Jakub Gladykowski wrote:
On Friday, March 11, 2016 at 1:01:01 PM UTC+1, Simon
On Friday, March 11, 2016 at 1:01:01 PM UTC+1, Simon Richter wrote:
>
> This seems like a good time to ask what you *actually* want to do[1].
>
>Simon
>
> [1] http://xyproblem.info/
>
I need to reboot slave few times during test. So whenever slave goes back
online, I need to execute anot
Hi,
On 11.03.2016 12:38, Jakub Gladykowski wrote:
> However all I want
> to do, is to trigger this job, only on the slave / node that just connected.
This seems like a good time to ask what you *actually* want to do[1].
Simon
[1] http://xyproblem.info/
--
You received this message because
http://wiki.jenkins-ci.org/display/JENKINS/Startup+Trigger will trigger
build, whenever slave / node will connect. You can restrict on which slaves
this build will be triggered, by using labels. However all I want to do, is
to trigger this job, only on the slave / node that just connected.
I the