Issue Type: Bug Bug
Assignee: Kohsuke Kawaguchi
Components: ssh-slaves
Created: 14/May/14 1:02 AM
Description:

We have our Linux SSH slaves configured like this:

  • Availability: Take this slave online according to a schedule
  • Startup Schedule: H 7 * * *
  • Period: 1380 minutes

Every morning at 9am, I come in and many slaves are marked as "suspended". The startup schedule would have them start up at 7am, although the UI does not make it clear which time zone the startup schedule is interpreted in.

Another point of oddness is that every slave it happens on has a "stuck" build job which has not yet finished. I am not sure whether the job is stuck because Jenkins tried to take the slave offline while the job was running, or if having a job running when shutdown is supposed to occur causes some bug with the shutdown scheduling.

This is possibly related to JENKINS-11889 where they are changing the config and the slaves don't immediately come online.

Environment: Windows Server 2008, Java 7
Project: Jenkins
Priority: Major Major
Reporter: trejkaz
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to