[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Mark Waite commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Grigoriy, could you submit a separate bug report for your Integrity SCM bug. This bug is specific to Git and the Git plugin and your Integrity information will be lost within this bug, since I'm sure the maintainer of the Integrity SCM plugin does not read Git plugni bug reports. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Mark Waite edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Grigoriy, could you submit a separate bug report for your Integrity SCM bug? This bug is specific to Git and the Git plugin and your Integrity information will be lost within this bug, since I'm sure the maintainer of the Integrity SCM plugin does not read Git plugni bug reports. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Grigoriy Milman commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured We have the same issue with Jenkins ver. 1.547. We updated from 1.535 to the 1.546 and suddenly this issue appeared. We are using PTC plugin, and for all build jobs each time when a polling happened the new build is triggered, polling log tells that there is so many changes found, but SCM tells that there is no changes! See attached screens 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Grigoriy Milman updated JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Change By: Grigoriy Milman (13/Jan/14 7:57 PM) Attachment: view1.JPG Attachment: View2.JPG 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Grigoriy Milman edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured We have the same issue with Jenkins ver. 1.547. We updated from 1.535 to the 1.546 and suddenly this issue appeared. We are using PTC plugin, and for all build jobs each time when a polling happened the new build is triggered, polling log tells that there is so many changes found, but SCM tells that there is no changes! See attached pictures - noticed that here "No changes" and SCM change log tells 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Grigoriy Milman updated JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Here is log files of one of the typical build started without any changes! Change By: Grigoriy Milman (13/Jan/14 9:14 PM) Attachment: IntegritySCM.zip 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Eric Shalov commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Solved! Encountered the problem on Jenkins ver. 1.540 with Git plugin 2.0. In my case, the scm-polling.log in /var/lib/jenkins/jobs/jobname/ showed that Jenkins couldn't connect to the Git server (while we were having a Git server outage). Since it failed to contact Git, the workspace was the same from the previous job run, so it thought again that it had new code in the repo and kept running the job. Solution: /sbin/service jenkins stop rm -rf /var/lib/jenkins/jobs/*/workspace /sbin/service jenkins start (Make sure you didn't need anything that was in ./*/workspace!!!) You can also setup the job to clean out the workspace/ after the job runs. To verify that you have connectivity to your Git server from the Jenkins server: jenkins$ telnet git.yourcompany.com 9418 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Mark Waite commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Eric, that technique does not solve it for me when using the JGit implementation. Were you using the command line implementation, or the JGit implementation with the plugin? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Mark Waite edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Eric, that technique does not solve it for me when using the JGit implementation. Were you using the command line implementation, or the JGit implementation with the plugin? In my case, I wiped the workspace, and confirmed that the multiple executions were all performing a checkout of the same git version, even though they were reporting that changes were detected. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Dave Close commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured My situation may not precisely match the parameters of this ticket. However, FWIW, here's my observation. I have 22 jobs that are nearly identical. One was created, the others were cloned from it. (New job, copy existing job...) The only differences between these jobs are their names and the names of the GIT repositories they access. The build steps are identical. All were set to trigger a build on a GIT change and all do that. 21 of them perform the build and then go back to an idle state. One performs the build, then about five minutes later does it again. And again. And again. (The trigger timing was set to "H/5 * * * *".) The GIT change trigger has been removed from that errant job and now I have to spawn it manually. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Dave Close edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured My situation may not precisely match the parameters of this ticket. However, FWIW, here's my observation. I have 22 jobs that are nearly identical. One was created, the others were cloned from it. (New job, copy existing job...) The only differences between these jobs are their names and the names of the GIT repositories they access. The build steps are identical and include wiping the workspace. All were set to trigger a build on a GIT change and all do that. 21 of them perform the build and then go back to an idle state. One performs the build, then about five minutes later does it again. And again. And again. (The trigger timing was set to "H/5 * * * *".) The GIT change trigger has been removed from that errant job and now I have to spawn it manually. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Mark Waite commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Can those who are encountering the problem identify anything specific about their configuration which exposes the problem? I've found that I see the problem with Git plugin 2.0 and Git client plugin 1.4.6 if I use JGit as the implementation, but I don't see the problem if I use Git command line as the implementation. I've seen the problem on all the platforms I tested, including Windows 8 x64, Windows 7 x86, Windows Home Server 2011, Debian Wheezy x64, and Debian Testing x64. I can't duplicate the problem when using the git command line implementation, yet the JGit implementation did not become widely used until after the release of Git plugin 2.0. If you can't deduce what is distinctive about your job that makes it build too frequently, would you be willing to upload sample job definitions which show the problem? The job definitions can then be compared with job definitions which do not poll too frequently in hopes there are clues in the differences between the jobs. Some questions: Does the too frequent building happen even after the workspace has been wiped? Does the too frequent building happen even on a copy of the job? Does the too frequent building happen on jobs using the git command line implementation? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Ken Raffenetti commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured I find that my build gets triggered over and over by an SCM Change even when the repository has not been updated. I updated Jenkins to 1.518 today and still see this behavior. Git plugin is 1.4.0. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Frank Meissner commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured I also have no trigger whatsoever configured in some a job, since the job is parametrised. I ended up cloning the project through a shell script build step. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Frank Meissner edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured I also have no trigger whatsoever configured in one job, since this job is parametrised. I ended up cloning the project through a shell script build step. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Frank Meissner edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured I also have no trigger whatsoever configured in one job, since this job is parametrised. I ended up cloning the project through a shell script build step. My jenkins version is 1.512. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Frank Meissner edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured I also have no trigger whatsoever configured in one job, since this job is parametrised. I ended up cloning the project through a shell script build step. My jenkins version is Jenkins ver. 1.512. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Alexander Uvizhev created JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 15/Apr/13 2:13 PM Description: Hi, Recently I've upgraded Jenkins to ver 1.508 and many plugins (including Jenkins GIT plugin from 1.1.25 to 1.3.0) and since that time I got a lot of my jobs using Git SCM running very frequently without any reason. None of my jobs using "Poll SCM" in "Build Triggers". But I see them running with build cause "Started by an SCM change" though very often there are no changes at all. And Polling Log is always empty. Project: Jenkins Priority: Major Reporter: Alexander Uvizhev 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
