Sorry, I was running that code without the job waiting. Now that I fired up
the build Label.get("mylabel").nodeProvisioner.stat.computeQueueLength()
returns 1. But still the node is not coming up automatically with the
message All node of label 'mylablel' are offline.
Il giorno giovedì 21 maggio 2015 20:03:16 UTC+2, Simone Dalmasso ha scritto:
>
> Thanks for the quick answer, I changed my_label to mylabel just to avoid
> underscores but, as you say, println(
> Label.get("mylabel").nodeProvisioner.stat.computeQueueLength() ) returns 0.
> While
> println(Jenkins.getInstance().unlabeledNodeProvisioner.stat.computeQueueLength()
>
> ) returns 0 as well.
>
> If I understand correctly there's nothing that I can do to solve this at
> the moment right?
>
> Il giorno giovedì 21 maggio 2015 17:52:44 UTC+2, Suckow, Thomas J ha
> scritto:
>>
>> Assuming you have things configured correctly I would believe it is
>> related to https://issues.jenkins-ci.org/browse/JENKINS-27034
>>
>> To confirm:
>> In the groovy console /script you can try the following replacing
>> my&&label with your my_label expression. If it prints 0, I'd bet it is
>> the issue above.
>> println( Label.get("my&&label").nodeProvisioner.stat.computeQueueLength()
>> )
>>
>> Also somewhat related, the following will print 1 but should be 0
>> println(Jenkins.getInstance().unlabeledNodeProvisioner.stat.computeQueueLength()
>>
>> )
>>
>> My workaround is to visit /updateCenter/ and check the restart box,
>> this will usually cause the cloud slave to be started. For me it happens
>> with the docker cloud "randomly" and certainly has "moods"
>>
>> From: Simone Dalmasso <[email protected]>
>> Reply-To: "[email protected]" <[email protected]>
>> Date: Thursday, May 21, 2015 at 8:17 AM
>> To: "[email protected]" <[email protected]>
>> Subject: [EC2 plugin] All nodes of label 'my_label' are offline
>>
>> Hi everyone,
>>
>> I'm using the EC2 plugin and I recently added a second AMI
>> configuration in the cloud tab with a label to use within a job.
>> Unfortunately the job is not launching the node when I trigger a build. I
>> have to do it manually from the jenkins -> manage nodes section.
>> I have another job using another node and is just working fine. I
>> restrict the jobs to the nodes using the labels and there are no specific
>> differences between the first and the second configurations apart from the
>> label and the instance type.
>>
>> Am I doing something wrong or do you have any suggestions?
>>
>> Thanks in advance
>>
>> --
>> 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/f8cfad5b-c55a-42b2-8e26-bfb576b63bba%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/f8cfad5b-c55a-42b2-8e26-bfb576b63bba%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/8d7556be-72ff-4065-ba24-a5a32d5c6599%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
