[JIRA] [git-plugin] (JENKINS-30350) Jobs get triggered twice from polling git scm

Confirm with Jenkins 2.42 and most of plugin is the latest version at this moment.
I agree with Klemen Ferjančič . My scenario is following:

Jenkins queue is 5 items.
each build takes 2 hours.
GIT polling for 15 minutes.

When there is a new git commit, GIT polling will queue a build because all executors is busy.
After 15 minutes, this build still in queue because all executors is still busy. At this moment, GIT polling will check again then it queue a new build because "Last Built Revision" remains.
Result: there are two the same build which are queued, in the the Jenkins queue.

My suggestion:
GIT polling should check whether a similar build is queued.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

12gonzo12@gmail.com (JIRA)

unread,

Jun 12, 2018, 12:58:01 PM6/12/18

to jenkinsc...@googlegroups.com

Christian commented on

I've noticed the issue on multibranch pipelines that use polling. Say a build for a branch takes 10 minutes to run and polling occurs every 2 minutes. If branch A gets committed then branch B gets committed, Jenkins will keep duplicating jobs for branch B every two minutes. This is because Jenkins checks branch B to see if the latest has been built and if not schedules a build, regardless of if one has already been scheduled.

Klemen Ferjančič is correct that Jenkins saves the sha1 when the build is started, but if the build for that branch cannot be started yet because another build is running then multiple builds will keep queuing up. Could the sha1 be saved once the build is queued? Could there be a way to block Jenkins from queuing more than 1 build from the same branch at a time? Is there a better way to prevent duplicate builds from being queued?

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

mark.earl.waite@gmail.com (JIRA)

unread,

Jun 12, 2018, 1:01:03 PM6/12/18

to jenkinsc...@googlegroups.com

Mark Waite assigned an issue to Unassigned

Jenkins /

Jobs get triggered twice from polling git scm

Change By:	Mark Waite
Assignee:	Nicolas De Loof

martyscheil+jenkins@gmail.com (JIRA)

unread,

Dec 13, 2018, 10:02:04 AM12/13/18

to jenkinsc...@googlegroups.com

Marty S commented on

I'm having the exact same scenario as Christian.

Does anyone have a workaround yet?

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

12gonzo12@gmail.com (JIRA)

unread,

Dec 13, 2018, 10:08:06 AM12/13/18

to jenkinsc...@googlegroups.com

Christian edited a comment on

Unfortunately the only thing that seems to work is either switching to hooks (which we can't do for reasons ) or increase the time between polling. Of course, by increasing the time between polling, your builds will trigger less frequently. We have ours at about 1 hour, which means there could be a delay of up to 1 hour between the time someone commits and the time Jenkins picks it up. I really wish someone would fix this bug, but seeing as it has been around for over 3 years I don't think it will happen.

12gonzo12@gmail.com (JIRA)

unread,

Dec 13, 2018, 10:08:06 AM12/13/18

to jenkinsc...@googlegroups.com

Christian commented on

Unfortunately the only thing that seems to work is either switching to hooks (which we can't do) or increase the time between polling. Of course, by increasing the time between polling, your builds will trigger less frequently. We have ours at about 1 hour, which means there could be a delay of up to 1 hour between the time someone commits and the time Jenkins picks it up. I really wish someone would fix this bug, but seeing as it has been around for over 3 years I don't think it will happen.

caratorn@gmail.com (JIRA)

unread,

Feb 22, 2019, 5:49:03 PM2/22/19

to jenkinsc...@googlegroups.com

Charles Clement commented on

We were seeing the same problem happen consistently for our project, every time a change would be commited to git, two builds were being triggered with our job setup to poll for new changes every 2 minutes.

But checking out our repository takes more than 4 minutes. So i assume the commit id is being stored right after the checkout has finished, which is why it was only 1 build that was always being queued up.

I would recommend setting the poll schedule to a value that will definitely allow for a full repository checkout before polling again. In our case, 6 minutes seems to be doing the trick.

maheshkumar3459@gmail.com (JIRA)

unread,

Apr 16, 2019, 7:47:02 AM4/16/19

to jenkinsc...@googlegroups.com

Maheshkumar Jeyaraj commented on

Klemen Ferjančič We are also facing the same issue. Upon investigating this can reproducible, When you close the Source branch after the Merge request.

Jenkins triggers multiple builds for the each push

nikhilnanal1@gmail.com (JIRA)

unread,

Nov 7, 2019, 7:29:04 PM11/7/19

to jenkinsc...@googlegroups.com

nikhil nanal commented on

I am facing this issue as well with Multibranch pipelines on Jenkins 2.164 LTS and exactly as described by Christian above, my polling interval is 2 minutes and builds take longer. when there is pending build it gets retriggerred multiple ( arbitrary number) of times