[JIRA] (JENKINS-49544) Cron job starting 12 hours later than scheduled

2018-03-19 Thread db...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-49544  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cron job starting 12 hours later than scheduled   
 

  
 
 
 
 

 
 Check the https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump to see whether a trigger thread is busy e.g. with networking. Some SCM related plugins do crazy stuff in the trigger thread.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49544) Cron job starting 12 hours later than scheduled

2018-03-02 Thread o.v.nenas...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49544  
 
 
  Cron job starting 12 hours later than scheduled   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 core  
 
 
Component/s: 
 other  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49544) Cron job starting 12 hours later than scheduled

2018-02-13 Thread roha...@nextcapital.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Rohacs created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49544  
 
 
  Cron job starting 12 hours later than scheduled   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 other  
 
 
Created: 
 2018-02-13 22:17  
 
 
Environment: 
 2.89.3  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Adam Rohacs  
 

  
 
 
 
 

 
 We have Jenkins jobs set to run overnight as they take hours to run. The last 2 days, the jobs kicked off as normal. The 3rd day, instead of running at 7pm-8pm (based on H in cron setting), the jobs started a full 12 hours later at 7am.  The cron job looks like this: H 19 * * 0-6 The time zone is set to America/Chicago in Jenkins and on the Linux server.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment