Is there a way to set a jenkins job to fail a multiconfiguration job if one of its children have been sitting in the queue for more than x amount of time?
I have set up a multiconfiguration job to run maintenance on every node in our system on a regular basis. However, if a node is down, its child job will sit there in the queue until either I kill the job or bring the machine back online so the child will run. My problem is that if the job for this agent is sitting there in the queue (obviously with its parent still active), the next iteration of the maintenance will not run for any node since there's already one running since it won't start the next build. I could set it to allow concurrent builds, but then the build queue would just get backed up with multiple parent builds after a while (and child jobs for the node that's down), if this node remains down. Ideally I'd like to be able to say "for job X", if it still has a child build in the queue for over x minutes, kill the queue entry. I've looked at the build timeout plugin, but that only works for jobs that are already running, not those still in the queue. Any suggestions? Scott -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
