The short version of what is happening is that a configuration schedule eventually stops running even though the UI reports it as unpaused. I say "stops running" because when I inspect the server log the "checking build condition on node..." log chunk stops appearing. The behavior is inconsistent: for some amount of time the schedule will appear in the server log, trigger builds (if the condition passes), and return to the schedule.
My build condition on the configuration is the following
groovy:
def repo = vars.getValue('scheduleRepository');
def configName = configuration.getName();
def isChanged = repositories.get(repo).isChanged();
if (isChanged)
logger.info('Schedule repository "' + repo + '" is changed... [' +configName+']');
else
logger.info('Schedule repository "' + repo + '" has NOT changed... ['+configName+']');
return isChanged;
The schedule is a periodic schedule that runs every 60s. This configuration steps will snapshot the 'scheduleRepository', pause the schedule, promote the actual build, and the actual build will then unpause the configuration after completing.
Could you possibly explain under what conditions a message like the following appears in the server log
2018-04-17 10:16:32,313 [pool-1-thread-13715] INFO com.pmease.quickbuild.DefaultBuildEngine - Processing build request (configuration:root/Whatever, request id:<id>)
or does not appear? It would seem that something other than simply the "pause/unpause" state of the schedule is determining whether it will be evaluated?
We are running quickbuild 7.0.13. Happy to provide more information if you need it. Hopefully I am missing something obvious here...