Unfortunately, I don't have a lot to add to the subject. The job has SCM but no triggers -- it is triggered using the Parameterized Trigger Plugin.
Yesterday we noticed that it was running continuously (using default parameters), restarting as soon as it finishes the previous build. The builds indicate that they were started by SCM change, but that there were no changes. There have been no new commits in the (git) SCM. Disabling and then enabling the job stopped it from building, but once it was triggered again (manually) it once again built continuously until disabled. The logs don't show anything out of the ordinary, just that the job completes successfully: May 20, 2015 12:27:10 PM hudson.model.Run execute INFO: Update Machine #5372 main build action completed: SUCCESS Jenkins is 1.608 with a lot of plugins. There have not been any plugins installed or upgraded recently that might be the trigger to this problem. Any ideas or suggestions? Thanks, David -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b86cd641-0f67-4cd8-8d18-406f861f85f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
