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

Wed, 07 Nov 2012 07:38:45 -0800

I've got the same problem for Synergy CM and Jenkins 1.489. Jenkins 1.488 works fine.

07.11.2012 14:54:46 hudson.triggers.SCMTrigger$Runner runPolling
SCHWERWIEGEND: Failed to record SCM polling for hudson.maven.MavenModuleSet@32c3601b[xxx-continuous_1.6.0]
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
        at java.lang.String.substring(String.java:1937)
        at hudson.Launcher.inherit(Launcher.java:1068)
        at hudson.Launcher.access$100(Launcher.java:80)
        at hudson.Launcher$LocalLauncher.launch(Launcher.java:756)
        at hudson.Launcher$2.launch(Launcher.java:723)
        at hudson.Launcher$ProcStarter.start(Launcher.java:346)
        at hudson.Launcher$ProcStarter.join(Launcher.java:353)
        at hudson.plugins.synergy.impl.Commands.executeSynergyCommand(Commands.java:175)
        at hudson.plugins.synergy.util.SessionUtils.openSession(SessionUtils.java:87)
        at hudson.plugins.synergy.SynergySCM.pollChanges(SynergySCM.java:1062)
        at hudson.scm.SCM.poll(SCM.java:375)
        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)
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