Maybe you can configure the 'quiet period'? The default is set in the configuration screen, but you can also set it per job configuration.
On Tuesday, December 13, 2016 at 9:48:46 PM UTC-8, Christoffer Holmstedt wrote: > > Hi > I'm running a Jenkins server, latest 2.19 LTS release with a few pipeline > jobs. Each job is triggered by a post-commit hook in respective SVN > repository. The problem I have is that I expected Jenkins to only queue up > one similiar job if another job of the same pipeline is already running but > I get one build per commit. > > As an example: Job A is triggered by a post commit from Commit #1. The > build takes 5 minutes so if I commit #2 and #3 to the repository Jenkins > will queue up two more builds, one for each commit. I would expect Jenkins > to only queue one extra build with commit #2 and #3. > > While searching for a solution to this it is not clear what the expected > behaviour is. Jenkins will only queue up one identical build if multiple > remote triggers are actived except in the case if a build uses parameters > in that case if the parameters are different each build will be unique. The > problem here is that I don't use parameterized builds so not sure what is > going on really and what to expect. > > Any help is appreciated. > > Best regards > -- > Christoffer Holmstedt > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/91be60dd-e5b5-4a93-b59f-2c9dc53a5090%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
