Matteo Centonza kirjoitti 5.2.2013 kello 10.45:
> But in case of master failure, even if running on slaves machines perfectly
> fit, jobs would be abrouptly stopped just because master <-> slave channel
> is interrupted.
Yes, if the master or slave breaks, you will always get a failed build. Th
them is a High Availability plugin. This
>> specifically allows you to fail over to a second Jenkins master on the fly
>> if the master dies.
>>
>> ** **
>>
>> --Rob
>>
>> ** **
>>
>> *From:* jenkinsci-users@go
t get
>> otherwise, and one of them is a High Availability plugin. This specifically
>> allows you to fail over to a second Jenkins master on the fly if the master
>> dies.
>>
>>
>>
>> --Rob
>>
>>
>>
>> From: jenkinsci
ps.com] *On Behalf Of *Matteo
> *Sent:* Tuesday, January 22, 2013 2:24 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* jenkins clustering
>
> ** **
>
> Hello,
>
> ** **
>
> first i'd like to thank developers for this great project.
&g
@googlegroups.com
Subject: jenkins clustering
Hello,
first i'd like to thank developers for this great project.
I'm sorry if already asked but i'm new on this list and searching the web
has produced no results.
We have a jenkins installation with 1 master and 5 slaves connected through ssh.
There is no such way. If this is critical to you, maybe you could check if you
can turn your builds into "external jobs" like described in
https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs
-- Sami
Matteo kirjoitti 22.1.2013 kello 21.23:
> Hello,
>
> first i'd like to thank
Hello,
first i'd like to thank developers for this great project.
I'm sorry if already asked but i'm new on this list and searching the web
has produced no results.
We have a jenkins installation with 1 master and 5 slaves connected through
ssh.
We are mostly a java shop and jenkins is central
