[JIRA] (JENKINS-39033) Job not stopped after AccuRev authentication failure

[a...@90a.nl (JIRA)]

Title: Message Title

Arno Moonen commented on JENKINS-39033   Re: Job not stopped after AccuRev authentication failure You are right. The job is stopped in v0.7.3. However, I get the following error when using this version (I filtered out the name of the job): [SOME-PROD-SW] $ "C:\Program Files\AccuRev\bin\accurev.exe" login -H accurev:5050 CI ******** FATAL: Failed authentication. Please re-try the 'login' command. FATAL: login ("C:\Program Files\AccuRev\bin\accurev.exe" login -H accurev:5050 CI ******) failed with exit code 1 ERROR: Failed to record SCM polling for com.tikal.jenkins.plugins.multijob.MultiJobProject@1bbdea7[PRODUCTS/SOME-PROD-SW] 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) The client I'm currently working for does not use passwords for AccuRev (so they fill in a username and leave the password field blank). Might this be the cause of this issue? Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.