Details
-
Bug
-
Status: Reopened (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
CentOS, jenkins ver 1.424.6
Description
We have noticed some intermittent issues with the 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.
Attachments
Activity
Wael Darwich
added a comment - I've been checking this for awhile, and noticed that in rare case polling starts on time, but it does not use the current script in the job configuration, it uses a previous version of it!! the script is a simple echo message, when I changed the script to echo a different message it was using an old one!!!
Wael Darwich
added a comment - I've been checking this for awhile, and noticed that in rare case polling starts on time, but it does not use the current script in the job configuration, it uses a previous version of it!! the script is a simple echo message, when I changed the script to echo a different message it was using an old one!!! Unfortunately, I can't reproduce it.
It is OK in my environment.
@wael for your previous issues, please could you test from ScriptTrigger 0.30.
Gregory Boissinot
added a comment - - edited Unfortunately, I can't reproduce it.
It is OK in my environment.
@wael for your previous issues, please could you test from ScriptTrigger 0.30.
Lyubomir Raykov
added a comment - In our environment we experienced the same issue. It happens when the process which the trigger was running freezes.
In our case the Shell script from the trigger runs a Java tool which freezes and the triggers for all jobs stop.
When the process is killed, the triggers start running again.
Lyubomir Raykov
added a comment - In our environment we experienced the same issue. It happens when the process which the trigger was running freezes.
In our case the Shell script from the trigger runs a Java tool which freezes and the triggers for all jobs stop.
When the process is killed, the triggers start running again. Gregory , i have got the same issue as Wael on ScriptTrigger 0.30. (the issue is as same as 2th issue of description)
MY jenkins version is 1.6.05
IN addition , could you have a workaround for that issue?
John Wang
added a comment - - edited Gregory , i have got the same issue as Wael on ScriptTrigger 0.30. (the issue is as same as 2th issue of description)
MY jenkins version is 1.6.05
IN addition , could you have a workaround for that issue? 
I used this plugin for long time, and when I had to move to a different server and create new Jenkins system and reinstall all plugins I started getting this error, now I only get for my job "Polling has not run yet." and I get it always!
I am using Jenkins ver. 1.517 and scripttrigger 0.28