We have run into an issue with mass rebuilds on the CI side where we will get thousands of messages across either Fedora or Red Hat message buses. I've looked into projects like https://github.com/jenkinsci/throttle-concurrent-builds-plugin to help limit it, but Jenkins itself gets very angry when it has hundreds, let alone thousands, of jobs queued up to run regardless if a runner is doing any work.
Ideally, we could tell jms-messaging to limit the number of consumed messages to be say 25 (or 50, 100, etc) and not grab more until we ack/close out the messages we are already working on.
However, if there's some Jenkins way to do this and I'm just missing something obvious, I am open to suggestions or ideas. :)
Feature Request
We have run into an issue with mass rebuilds on the CI side where we will get thousands of messages across either Fedora or Red Hat message buses. I've looked into projects like https://github.com/jenkinsci/throttle-concurrent-builds-plugin to help limit it, but Jenkins itself gets very angry when it has hundreds, let alone thousands, of jobs queued up to run regardless if a runner is doing any work.
Ideally, we could tell jms-messaging to limit the number of consumed messages to be say 25 (or 50, 100, etc) and not grab more until we ack/close out the messages we are already working on.
However, if there's some Jenkins way to do this and I'm just missing something obvious, I am open to suggestions or ideas. :)