[
https://issues.jenkins-ci.org/browse/JENKINS-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159691#comment-159691
]
Peter Kline commented on JENKINS-9596:
--------------------------------------
This is no longer an issue for us after using the method by Kohsuke:
http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
> SCM polling with GIT creates Spurious Builds with "No Changes"
> --------------------------------------------------------------
>
> Key: JENKINS-9596
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9596
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Reporter: Charles Scalfani
> Assignee: abayer
> Priority: Minor
> Attachments: config.xml
>
>
> I see many builds when pushes to non-master branches (I'm only pulling from
> the master branch). The build is triggered by SCM change but the master
> branch has the same ID. Here is a discussion on StackOverflow where others
> are encountering the same problem
> (http://stackoverflow.com/questions/5784329/how-can-i-make-jenkins-ci-with-git-trigger-on-pushes-to-master).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
