[JIRA] (JENKINS-61065) Git plugin: infinite build trigger by "SCM change"

writeback2pooja@gmail.com (JIRA)

unread,

Feb 12, 2020, 4:02:05 AM2/12/20

to jenkinsc...@googlegroups.com

pooja shah created an issue

Jenkins /

JENKINS-61065

Git plugin: infinite build trigger by "SCM change"

Issue Type:	Bug
Assignee:	Mark Waite
Components:	git-plugin
Created:	2020-02-12 09:01
Environment:	Jenkins ver. 2.190.1 Jenkins Git plugin: 3.5.1
Priority:	Critical
Reporter:	pooja shah

It's giving nightmare with infinite builds marked as "Started by an SCM change" even if I start the build myself, one build is triggered on my name followed by infinite triggers by "SCM change" and there is no change in code at all.

Seeing these weird new lines
```
Multiple candidate revisions
Scheduling another build to catch up with
```
like https://issues.jenkins-ci.org/browse/JENKINS-54102?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

And this is happening for master branch but we don't have any "origin/master" branch as suggested workaround [here](https://issues.jenkins-ci.org/browse/JENKINS-21464?focusedCommentId=250183&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-250183)

Any fix?

*Update* Strangely, while we didn't have origin/master, replacing the wildcard find "*/master" with "master" in "Branches to build" fixes the issue. But, I have been using the same since ages (8 years now) and the wildcard has never given me this issue before. The Git plugin's "Scheduling another build to catch up with" implementation needs to be re-looked.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

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

unread,

Feb 12, 2020, 1:33:02 PM2/12/20

to jenkinsc...@googlegroups.com

Mark Waite updated an issue

Jenkins /

JENKINS-61065

Git plugin: infinite build trigger by "SCM change"

Change By:	Mark Waite

Exact similar to [https://github.com/jenkinsci/gitlab-plugin/issues/30]

It's giving nightmare with infinite builds marked as "Started by an SCM change" even if I start the build myself, one build is triggered on my name followed by infinite triggers by "SCM change" and there is no change in code at all.

Seeing these weird new lines
```
Multiple candidate revisions
Scheduling another build to catch up with
```
like https://issues.jenkins-ci.org/browse/ JENKINS-54102 ?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

And this is happening for master branch but we don't have any "origin/master" branch as suggested workaround [here ]( | https://issues.jenkins-ci.org/browse/JENKINS-21464?focusedCommentId=250183&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-250183 ) ]

Any fix?

**Update** Strangely, while we didn't have origin/master, replacing the wildcard find "*/master" with "master" in "Branches to build" fixes the issue. But, I have been using the same since ages (8 years now) and the wildcard has never given me this issue before. The Git plugin's "Scheduling another build to catch up with" implementation needs to be re-looked.

Add Comment

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

unread,

Feb 12, 2020, 4:29:02 PM2/12/20

to jenkinsc...@googlegroups.com

Mark Waite commented on

JENKINS-61065

Re: Git plugin: infinite build trigger by "SCM change"

Pull request 829 has been merged for the next release of the git plugin. Jobs may optionally choose to ignore multiple candidate revisions. You're welcome to test the latest git plugin build to confirm that change allows you to disable checks for multiple candidate versions. You'll need to download the ".hpi" file from that list of artifacts.