On Tue, Dec 11, 2012 at 2:20 AM, Gavin McDonald <[email protected]>wrote:
> > -----Original Message----- > > From: Dennis Lundberg [mailto:[email protected]] > > Sent: Monday, 10 December 2012 7:55 AM > > To: [email protected] > > Subject: Jenkins Windows slave unavailable again > > > > Hi > > > > The Windows slave "windows1" in our Jenkins instance has gone unavailable > > once again. It's been down for ~3½ days now. Can someone please try to > get > > it started again? > > I guess someone did , its working fine. > I did, didn't see this thread until now. > Note that ALL slaves are configured to turn off and wake up again when a > build asks it to, so just a general > note to everyone to be sure that the slave really is offline rather than > just waiting for a build to wake it. > That's not true for the Windows slave (but is for all others). That's part of what I would like to change with the Windows slave, having it controlled by the master rather than running on its own (where it looses the connection and fails). Just need to find the time to set it up and to fend of olamy when his Selenium tests start failing :) /niklas
