[JIRA] (JENKINS-14087) ScriptTrigger plugin timer issue
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-14087 ScriptTrigger plugin timer issue Change By: Alex Earl Component/s: plugin-proposals Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.144718.133952170.14187.1563373440502%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14087) ScriptTrigger plugin timer issue
Yan Qin commented on JENKINS-14087 ScriptTrigger plugin timer issue Hi, Greg: Thank you for your quick response. These 125 job scripttrigger do not happen at the same time. And each trigger takes within 1 minute. That means the probability of having many triggers at the same time is low. I checked all timestamp of log when trigger running normally. At most 3 job triggers happen at the same time. So that shall not be issue. But when I checked the timestamp of log when scripttrigger did not work, the timestamp of more jobs are same (maybe more than 3 but I do not remember very clearly). some of jobs use the same timer format 0 */3 * * *, 40 */2 * * * Will that be problem? Lastly, about your question to allan, slave is not off. In the jenkins web ui "scriptTrigger" only shows "polling is not run yet".And the scriptTrigger.log has no content although the timestamp shows it did recreate on time. So it does not looks like timer issue. It seems the log file is touched but can not proceed. Do not know where it is blocked. 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
[JIRA] (JENKINS-14087) ScriptTrigger plugin timer issue
amargono commented on JENKINS-14087 ScriptTrigger plugin timer issue Additional Info: In the jenkins UI, some jobs only shows "Polling has not run yet." Those jobs usually run scriptTrigger every 2-4 hours. And many runs at the same time based on timestamp. The timestamp shows the scriptTrigger-polling.log is created but can not be started because there is no content. So it looks timer trigger to start (at least log file is touched) but nothing is able to run. Is that due to too many scriptTrigger so exceed some thread limitation? We have tried to install ver 0.19 and 0.20 but it didn't work either. We notice that 0.13 fixed the open files issue and we will give it a try. Thanks, amargono 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
[JIRA] (JENKINS-14087) ScriptTrigger plugin timer issue
amargono updated JENKINS-14087 ScriptTrigger plugin timer issue Change By: amargono (05/Jul/12 6:05 PM) Component/s: scripttrigger 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
[JIRA] (JENKINS-14087) ScriptTrigger plugin timer issue
amargono updated JENKINS-14087 ScriptTrigger plugin timer issue Change By: amargono (05/Jul/12 6:03 PM) Summary: ShellTrigger ScriptTrigger plugin timer issue Description: We have noticed some intermittent issues with the ShellTrigger ScriptTrigger plugin build timer.The plugin version is 0.11.1.There are two issues:1. Sometime the build timer does not work per schedule,e.g., a job was run more frequently than the scheduled run time.2. Sometime the build timer does not work at all, e.g., there are no builds kicked off when a build supposedly to be kicked off per schedule. 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
