[JIRA] (JENKINS-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)

Tue, 06 Nov 2012 00:34:49 -0800

 
Régis Desgroppes edited a comment on Bug JENKINS-15718

I faced the same issue yesterday after installing Jenkins 1.489.
We're using Mercurial as SCM, so I guess the ticket affects all SCM plugins.

Nov 5, 2012 10:31:42 AM hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@60f38b42[reference_client_devel.centos5-x86_64.build]
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)


Temporarily solved by reinstalling Jenkins 1.488.
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

Reply via email to