| << Back to previous view |
|
[QB-2064] scheduled tasks not running
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.1.23 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Tim Earle | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | RHEL6 - ec2 | ||
| Description |
|
The scheduler appears to not be functioning as designed. The periodic/interval does not execute, nor does recurring cron schedules.
Set-time schedules such as "0 0 12 * * ?" function, but " 0 0 * * * ?" does not. If these are running, it is not showing up in the build log. |
| Comments |
| Comment by Robin Shen [ 28/May/14 05:22 AM ] |
|
Probably the configuration is fired but new build is not generated due to the fact that build condition is not satisified. To verify, please check in server log of QB to see if it contains message such as around the schedule time:
Build condition not satisfied, new build won't be generated. |
| Comment by Tim Earle [ 28/May/14 07:19 PM ] |
|
Is there any way to determine what is causing the build condition to fail? Perhaps an error or warning if this happens during a scheduled configuration..
2014-05-28 01:23:25,085 [pool-1-thread-1045] INFO com.pmease.quickbuild.DefaultBuildEngine - Checking build condition on node 'host:8810'... 2014-05-28 01:23:25,086 [pool-1-thread-1046] INFO com.pmease.quickbuild.CheckConditionJob - Taking repository snapshots... 2014-05-28 01:23:25,088 [pool-1-thread-1046] INFO com.pmease.quickbuild.CheckConditionJob - Evaluating build condition... 2014-05-28 01:23:25,099 [pool-1-thread-1045] INFO com.pmease.quickbuild.DefaultBuildEngine - Build condition not satisfied, new build won't be generated. 2014-05-28 01:23:25,099 [pool-1-thread-1045] INFO com.pmease.quickbuild.DefaultBuildEngine - Build request has been processed |
| Comment by Robin Shen [ 29/May/14 12:31 AM ] |
| By default the condition is set to only run build if there are changes found in SCM. If however you are using complicated scripts to calculate build condition, you may put some log information in the script body to help identifying the problem. |
| Comment by Tim Earle [ 17/Jun/14 02:03 PM ] |
|
Thanks Robin,
It was failing on the SCM changes as you described. Is there any way to make the reason why it failed (such as build-condition) appear in the interface? While it might not be an error, it should still indicate that the scheduled job didn't execute for a reason. Thanks! |
| Comment by Robin Shen [ 18/Jun/14 12:19 AM ] |
|
We'd rather not to display this as an error if the build condition evaluation itself does not report an error, as otherwise, almost all configurations not necessary being built will be cluttered with such message. If you want to make the reason obvious, just throw a QuickbuildException in your build condition evaluation script.
I am closing this issue now, feel free to reopen it if you still feel like this is a problem. |