-
Bug
-
Resolution: Fixed
-
Minor
-
None
I've noticed this several times now since upgrading to a version of the accurev plugin greater than 0.6.
After some time (timing really varies from minutes to hours) the authentication with AccuRev fails and I see this stack trace in the polling log:
ERROR: Failed to record SCM polling for com.tikal.jenkins.plugins.multijob.MultiJobProject@4ac441[PRODUCT/SOME-PRODUCT] java.lang.IllegalArgumentException: Authentication failure at hudson.plugins.accurev.delegates.AbstractModeDelegate.setup(AbstractModeDelegate.java:64) at hudson.plugins.accurev.delegates.AbstractModeDelegate.compareRemoteRevisionWith(AbstractModeDelegate.java:92) at hudson.plugins.accurev.AccurevSCM.compareRemoteRevisionWith(AccurevSCM.java:450) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:391) at hudson.scm.SCM.poll(SCM.java:408) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1482) at hudson.model.AbstractProject._poll(AbstractProject.java:1452) at hudson.model.AbstractProject.poll(AbstractProject.java:1363) at com.tikal.jenkins.plugins.multijob.MultiJobProject.poll(MultiJobProject.java:95) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:528) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:574) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(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)
Strange thing is that after this failure, the children of this multijob are being executed (as mentioned JENKINS-39033).
Looking at the error log of the Jenkins master server, I see this error for all of my jobs.
I've tried to configure the plug-in with different options set in the Jenkins configuration for the AccuRev plug-in, but so far it seems that this occurs regardless of the configuration options for the plug-in.
The logs of the AccuRev server do not even show a failed log-in attempt and restarting the Jenkins master server (temporarily) solves the problem.
Therefore, I suspect an error in the plug-in.