The same behaviour with 1.610
On Thursday, 16 April 2015 17:16:36 UTC+3, Jānis Balodis wrote:
>
> Hi,
>
> Further more, the first build after Jenkins master restart works fine
> (Docker node is started and build completed). After that nodes are spawned,
> I can see that sshd
Considering that Jenkins stores all the configuration there, it is a
solution that will work.
Regarding slaves, there shouldn't be any useful information at all. All you
should do is update node settings to point to new servers.
On Thursday, 16 April 2015 16:28:54 UTC+3, Ashish Yadav wrote:
>
>
works. If I'll click on "Launch slave agent" on a node that
initially failed to start, it will launch.
Regards,
Janis
On Thursday, 16 April 2015 12:37:37 UTC+3, Jānis Balodis wrote:
>
> If you are referring to docker plugin then tried that too, last week
> though...
&
On Thu, Apr 16, 2015 at 10:13 AM, Jānis Balodis > wrote:
>
>> Hi,
>>
>> I've experienced a similar behaviour, but with docker plugin v 0.8 and
>> Jenkins starting from version 1.606 till 1.609. If with 1.606 it is still
>> possible to run builds, eve
Hi,
I've experienced a similar behaviour, but with docker plugin v 0.8 and
Jenkins starting from version 1.606 till 1.609. If with 1.606 it is still
possible to run builds, even though sometimes agents failed to start, 1.609
was impossible to use and I rolled back to 1.605. And this behaviour
