Jobs running under a build matrix do not get put in the queue

[Jeffrey Parker]

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?

[Scott Evans]

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 <thex...@gmail.com> 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 jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeffrey Parker]

It looks like it is actually adding the job to the queue, but eventually that drops out of the queue and never runs.

--
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 jenkinsci-use...@googlegroups.com.

[Jeffrey Parker]

I would also point out that I just started a build manually that went into the queue and maybe 10 minutes of waiting in the queue it was not there anymore. This is strange because I have seen jobs wait in the queue for days before when a job gets stuck.

[Les Mikesell]

On Tue, Nov 4, 2014 at 11:11 AM, Jeffrey Parker <thex...@gmail.com> wrote:
> I would also point out that I just started a build manually that went into
> the queue and maybe 10 minutes of waiting in the queue it was not there
> anymore. This is strange because I have seen jobs wait in the queue for days
> before when a job gets stuck.

If you mouse-hover over the job showing in the queue, does it show you
the resource it is waiting for?

--
Les Mikesell
lesmi...@gmail.com

[Jeffrey Parker]

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.

[Les Mikesell]

On Tue, Nov 4, 2014 at 11:49 AM, Jeffrey Parker <thex...@gmail.com> 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
lesmi...@gmail.com

[Jeffrey Parker]

Yes, that is the problem that I am encountering.

--
    Les Mikesell
      lesmi...@gmail.com

[Jeffrey Parker]

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.