I think I may have found a fix for the problem. The job execution was being limited by global settings, but when applying the same settings to the job itself it seems to be fixed. I still need to run more tests to be sure the issue is really resolved.
On Tue, Nov 4, 2014 at 11:55 AM, Jeffrey Parker <[email protected]> wrote: > Yes, that is the problem that I am encountering. > > On Tue, Nov 4, 2014 at 11:54 AM, Les Mikesell <[email protected]> > wrote: > >> On Tue, Nov 4, 2014 at 11:49 AM, Jeffrey Parker <[email protected]> >> wrote: >> > I know what it is waiting for, that is not the problem. It is waiting >> for >> > another job of the same type to finish because only one can run at a >> time. >> > >> >> That part is normal - or at least waiting on a resource that can run >> that type of job. Going away without running anything at all is not >> normal, though. >> >> -- >> Les Mikesell >> [email protected] >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-users/wvB4q1Bu5oQ/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/d/optout.
