[JIRA] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building Change By: Craig Rodrigues Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Andrew Erickson commented on JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building I just encountered this. You need to set the field in the advanced options (the second advanced option set) called "unique SCM name (optional)". It's not really optional when using this plugin (as the tip says). My builds are now not executing on every polling instance. Not sure if it's possible for plugins to make option fields required... but it would be nice if this did that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Dave Green commented on JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building Hi Andreas, I've encountered this issue as well, but have been able to work round it. My environment: Windows 2008 R2, Jenkins 1.475, Jenkins Multiple SCMs plugin 0.2, Git plugin 1.1.21, Git 1.7.4.msysgit.0 Workaround: I've been able to work around this issue by creating a separate job monitoring a single Git Repository (I'm only interested in changes in one, but you could set up a trigger job for each repository you are monitoring) and using this job to trigger my multi-SCM job. Obviously I set the polling on the multi-SCM job to be a very large interval or disable it (see below). Note that this workaround isn't ideal due to (1) additional jobs need to be created, and (2) More space is needed for an additional copy of the Repository being monitored. In the fullness of time I intend to set a very long polling interval and use Kohsuke Kawaguchi's instructions at http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ to get the triggers being "pushed" from Git instead of "pulled" from Jenkins. I believe that this should negate the need for the parent job. Hope that helps, Dave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Andreas created JENKINS-14019: - Summary: Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building Key: JENKINS-14019 URL: https://issues.jenkins-ci.org/browse/JENKINS-14019 Project: Jenkins Issue Type: Bug Components: multiple-scms Environment: Ubuntu 10, Jenkins 1.457, multiple-scms 0.2, Git 1.1.17, Git-Parameter 0.2 Reporter: Andreas Assignee: Kevin Bell Priority: Blocker I've extended a certain job with a project containing centralized build-scripts, thus I set the checkout-path to ../BUILD for this repo, the other remained unchanged. The build works fine, however, the build is triggered all 15 mins (Poll SCM = */15 * * * *), although nothing has changed in neither repo. The git-revision for both repos is shown correctly, only the plugin doesn't recognize it hasn't changed. This is a blocker for me that prevents me from using the plugin, because I can't afford 20 builds to run every 15 minutes. -- 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
