You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by sebb <se...@gmail.com> on 2017/02/24 10:27:21 UTC

Jenkins Windows nodes all broken

The Jenkins Windows nodes are all out of order.

1 & 2 have stopped

node 3 is running, but all the builds are failing because the home
directories appear to be read-only

Re: Jenkins Windows nodes all broken

Posted by Chris Thistlethwaite <ch...@apache.org>.
I just updated the perms on jenkins-win2012-3, builds should be working 
correctly now.

-CT


On 02/24/2017 04:25 PM, Chris Thistlethwaite wrote:
>
> On 2017-02-24 05:27 (-0500), sebb <se...@gmail.com> wrote:
>> The Jenkins Windows nodes are all out of order.
>>
>> 1 & 2 have stopped
>>
>> node 3 is running, but all the builds are failing because the home
>> directories appear to be read-only
>>
> Jenkins-win2012-1 and -2 are up, they were down around 7-8am EST. The third box is new, so we might have to work out some issues, though I was able to get a build done yesterday for ODFToolkit-Windows.
>
> Chris and I have put some monitoring up in Datadog so we can catch if they fail again.


Re: Jenkins Windows nodes all broken

Posted by Chris Thistlethwaite <ch...@apache.org>.

On 2017-02-24 05:27 (-0500), sebb <se...@gmail.com> wrote: 
> The Jenkins Windows nodes are all out of order.
> 
> 1 & 2 have stopped
> 
> node 3 is running, but all the builds are failing because the home
> directories appear to be read-only
> 

Jenkins-win2012-1 and -2 are up, they were down around 7-8am EST. The third box is new, so we might have to work out some issues, though I was able to get a build done yesterday for ODFToolkit-Windows. 

Chris and I have put some monitoring up in Datadog so we can catch if they fail again.