|
|
|
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! 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.
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 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. |
I am closing this issue now, feel free to reopen it if you still feel like this is a problem.