The same issue here after upgrading from 1.463 to 1.489. We use ClearCase. We get the following stack trace:

Nov 07, 2012 10:41:24 AM hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@a25509[ProdXProject]
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(Unknown Source)
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.plugins.clearcase.HudsonClearToolLauncher.getLaunchedProc(HudsonClearToolLauncher.java:153)
at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:114)
at hudson.plugins.clearcase.ClearToolExec.runAndProcessOutput(ClearToolExec.java:822)
at hudson.plugins.clearcase.ClearToolExec.catcs(ClearToolExec.java:84)
at hudson.plugins.clearcase.ClearCaseSCM.hasNewConfigSpec(ClearCaseSCM.java:302)
at hudson.plugins.clearcase.AbstractClearCaseScm.compareRemoteRevisionWith(AbstractClearCaseScm.java:670)
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(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

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