[Nfd-dev] Jenkins slave resiliency

[Junxiao Shi]

Dear folks

Right now, all Jenkins slaves hosted at CSU are down. CSU hosts all OSX
10.11 and 10.12 slaves. Therefore, none of the build jobs can complete.
This is not the first time that all slaves of a certain OS are failing at
the same time, and most likely this would not be the last.

How about deploying the nodes in a more resilient way?
*For each OS version, there should be slaves in at least two different
sites*.
This ensures the build jobs can proceed when there is at most one failure.

Yours, Junxiao

On Tue, Apr 3, 2018 at 11:03 Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> 20180402 NFD call discussed this issue.
>
> Beichuan reveals that Ashiq is going to take over Jenkins in May 2018.
> During the transition, he is going to learn how to deploy macOS slaves, and
> then he can start swapping nodes to be more resilient.
>
> There were also concerns about the Jenkins master being deployed at only
> one site, but there isn't a good solution yet.
>
> On Sat, Mar 31, 2018 at 10:04 PM, Junxiao Shi <
> shijunxiao at email.arizona.edu> wrote:
>
>> Dear folks
>>
>> Right now, all Jenkins slaves hosted at CSU are down. CSU hosts all OSX
>> 10.12 and 10.13 slaves. Therefore, none of the build jobs can complete.
>> This is not the first time that all slaves of a certain OS are failing at
>> the same time, and most likely this would not be the last.
>>
>> How about deploying the nodes in a more resilient way?
>> *For each OS version, there should be slaves in at least two different
>> sites*.
>> This ensures the build jobs can proceed when there is at most one failure.
>>
>> Yours, Junxiao
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20181027/36e86c1f/attachment.html>