Re: Jenkins failed to record SCM polling
This problem is fixed in Jenkins 1.491 (issue JENKINS-15733https://issues.jenkins-ci.org/browse/JENKINS-15733 ). My Mercurial is polling correctly now! Thank you! On Fri, Nov 9, 2012 at 2:48 AM, Mark Waite markwa...@yahoo.com wrote: You could consider switching to the long term support release. It arrives about once every three months and remains stable for those three months. Mark Waite -- *From:* KP koen.pollent...@gmail.com *To:* jenkinsci-users@googlegroups.com *Sent:* Thursday, November 8, 2012 2:02 AM *Subject:* Re: Jenkins failed to record SCM polling Exactly the same issue, but with (old built-in 1.x) CVS plugin. Issue went away after revert tot 1.488. After the lazy loading problem made jenkins unusable, now this... It seems the stability of the jenkins updates is getting very bad lately. 2 bugs completely breaking jenkins, only in a couple of weeks :-( -- Hez
Re: Jenkins failed to record SCM polling
Exactly the same issue, but with (old built-in 1.x) CVS plugin. Issue went away after revert tot 1.488. After the lazy loading problem made jenkins unusable, now this... It seems the stability of the jenkins updates is getting very bad lately. 2 bugs completely breaking jenkins, only in a couple of weeks :-(
Re: Jenkins failed to record SCM polling
You could consider switching to the long term support release. It arrives about once every three months and remains stable for those three months. Mark Waite From: KP koen.pollent...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Thursday, November 8, 2012 2:02 AM Subject: Re: Jenkins failed to record SCM polling Exactly the same issue, but with (old built-in 1.x) CVS plugin. Issue went away after revert tot 1.488. After the lazy loading problem made jenkins unusable, now this... It seems the stability of the jenkins updates is getting very bad lately. 2 bugs completely breaking jenkins, only in a couple of weeks :-(
Re: Jenkins failed to record SCM polling
The problem gone away after I downgraded Jenkins to 1.488. On Tue, Nov 6, 2012 at 5:20 PM, Dirk Kuypers kuypers.d...@gmail.com wrote: just vote for: https://issues.jenkins-ci.org/browse/JENKINS-15718 BR Dirk 2012/11/6 hezjing hezj...@gmail.com I made the conclusion too early, the problem is still there. The mercurial plugin is able to poll the changes for the 1st time, e.g. when the workspace directory is deleted. Then, it fails in the subsequent polling, e.g. when the workspace directory is created. On Tue, Nov 6, 2012 at 11:33 AM, hezjing hezj...@gmail.com wrote: Hi This problem is resolved by deleting the workspace directory. It looks like the problem occurred after Jenkins is restarted after the upgrade. On Tue, Nov 6, 2012 at 11:08 AM, hezjing hezj...@gmail.com wrote: Hi I'm using Jenkins 1.489 and Mercurial plugin 1.41. My Jenkins failed to poll Mercurial changes with the following error in the polling log: ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@3c32fb80[.] java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.Launcher$2.launch(Launcher.java:712) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) at hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Any idea? -- Hez -- Hez -- Hez -- Hez
Re: Jenkins failed to record SCM polling
I made the conclusion too early, the problem is still there. The mercurial plugin is able to poll the changes for the 1st time, e.g. when the workspace directory is deleted. Then, it fails in the subsequent polling, e.g. when the workspace directory is created. On Tue, Nov 6, 2012 at 11:33 AM, hezjing hezj...@gmail.com wrote: Hi This problem is resolved by deleting the workspace directory. It looks like the problem occurred after Jenkins is restarted after the upgrade. On Tue, Nov 6, 2012 at 11:08 AM, hezjing hezj...@gmail.com wrote: Hi I'm using Jenkins 1.489 and Mercurial plugin 1.41. My Jenkins failed to poll Mercurial changes with the following error in the polling log: ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@3c32fb80[.] java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.Launcher$2.launch(Launcher.java:712) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) at hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Any idea? -- Hez -- Hez -- Hez
