hmm, I don't follow you now tarocaravan. I only use post-commit hooks from SVN to Jenkins, no polling. Each SVN repository only triggers one job on the Jenkins build server but the problem is that a rapid sequence of multiple commits will build up the "feedback loop time". So one commit will give feedback in 5 minutes but the builds after the first commit will build up to total time of commits * 5 minutes, which is too long.
2016-12-15 6:08 GMT+01:00 <[email protected]>: > From my experience, having multiple pipeline jobs polling for changes > causes confusion from the end-user. It seems better to have one "master" > job that polls and runs all the other builds. Also it seems Jenkins jobs > (including pipeilnes) are quite happy to build concurrently, but I don't > know how to handle it yet. So I've selected "Do not allow concurrent > builds" in the master pipeline job. As a result, the job will queue. > > 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/9e6d8b89-2566-4bbe-b1ca-02685e2876c6%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/9e6d8b89-2566-4bbe-b1ca-02685e2876c6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAG9Fz%2Bv%3DvQRRo1e7uR4jFePZEXyoxfyNhV20h7gXdu%2BP46GCDQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
