I believe that Jenkins is is set to not put another build in the queue if one is already there, waiting to be run, if it is triggered manually by an upstream build. I do not know if this can be overridden in some way or not. I know in our instances, a Gerrit patch set that triggers a build can put several parent builds in the queue, but those then only execute one at a time so we don't have matrix child builds running in parallel.
Scott On Tue, Nov 4, 2014 at 10:40 AM, Jeffrey Parker <[email protected]> wrote: > I am posting here again since no one is responding to my problem anywhere. > I have a job in jenkins that has a build matrix that starts several jobs, > some of those jobs can only run one at a time. If I start the build matrix > job while another job is still running most of the time the jobs in the > build matrix are not going to the queue, instead the jobs are just not > running. Can someone help me fix this? > > -- > 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. > -- 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.
