Gerrit Trigger generating large queue of jobs

[Curtis Kline]

We have a repo with lots of development going on, and we want to trigger
builds using the Gerrit Trigger plugin (using change merged).
Unfortunately the plugin queues up builds on this repo every few minutes,
since we're checking in lots of changes. The builds take 25 minutes, so
right now there are six of these waiting in the queue.

Any suggestions on how to best control this? Ideally I'd like the Gerrit
Trigger not to put a job in the queue if there's already an instance of
that job waiting in the queue.

If we were still doing this with Git polling, we'd just reduce the polling
to every 20 minutes or so.

Any ideas would be appreciated.

Thanks,
Curtis

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Gerrit Trigger generating large queue of jobs

[teilo]

For our commit build we use a change hook on Gerrit that notifies Jenkins, Then 
just use normal git setup with polling @yearly.

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.