We're using ScriptTrigger and are finding it a great addition to Jenkins,
thanks for working on it.
We've recently added a lot more jobs using ScriptTrigger, and have run in
to a concurrency limitation.
Each job runs a script that takes a few seconds, and we'd like to poll very frequently.
However, we're finding that there's a limit to the number of jobs that we can have in this configuration as only one script is run at a time (despite the fact that we have many slaves to run the scripts)
I have two suggestions for improvements here:
1. Implement equals() on the Runnable objects so that the jenkins queue will drop duplicate jobs from the queue. This won't allow more to be run, but it will stop the queue from overflowing if the rate of jobs is greater than the single executor can handle.
2. Allow for configuration of the allowed concurrency, the same way the built-in SCM trigger does (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/triggers/SCMTrigger.java#L224). Then we could increase the concurrency to match the number of slaves and poll a lot more frequently.