hi,
the following does disconnect, but it did not change the reconnect behaviour :-(
import hudson.slaves.*
for (aSlave in hudson.model.Hudson.instance.slaves) {
if (aSlave.name == 'excon-34') {
println('Enabling NameOfSlave!');
aSlave.getComputer().disconnect(new OfflineCause.ByCLI("X"
Thanks for the snippet.
I will try it with "disconnec()", perhaps when done with API it will
act differently
--pawel
On Tue, Oct 16, 2012 at 3:42 PM, Dirk Kuypers wrote:
> Hi Pawel,
>
> 2012/10/16 Pawel Jasinski :
>> hi,
>>
>>
>> On Mon, Oct 15, 2012 at 5:05 PM, Marek Gimza wrote:
>>> Pawel,
>>>
Hi Pawel,
2012/10/16 Pawel Jasinski :
> hi,
>
>
> On Mon, Oct 15, 2012 at 5:05 PM, Marek Gimza wrote:
>> Pawel,
>>
>>
>> As an interim solution, you could have a build step that runs either a
>> groovy script or the Jenkins-cli to "disconnect-node" and "connect-node" .
>
> I have checked with the
Master does not reconnect slave if it was manually disconnected.
>>
>> I thing it would also help in situation when slave service is in the way
>> of
>> the things you do with slave. There is no way to tell master to simply
>> back
>> off until further notice.
>>
>>
>>
>> Cheers,
>> Pawel
>>
>>
>>
>> --
>> View this message in context:
>> http://jenkins.361315.n4.nabble.com/Automatic-reconnect-after-manual-disconnect-tp4643194.html
>> Sent from the Jenkins users mailing list archive at Nabble.com.
>
>
ituation when slave service is in the way of
> the things you do with slave. There is no way to tell master to simply back
> off until further notice.
>
>
>
> Cheers,
> Pawel
>
>
>
> --
> View this message in context:
> http://jenkins.361315.n4.nabble.com/Automatic-reconnect-after-manual-disconnect-tp4643194.html
> Sent from the Jenkins users mailing list archive at Nabble.com.
>
context:
http://jenkins.361315.n4.nabble.com/Automatic-reconnect-after-manual-disconnect-tp4643194.html
Sent from the Jenkins users mailing list archive at Nabble.com.
