jacekw created JENKINS-13032:
--------------------------------

             Summary: Updating cvs plugin to version 2.0 causes 
"java.lang.RuntimeException: CVS authentication failure while running rlog 
command"
                 Key: JENKINS-13032
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13032
             Project: Jenkins
          Issue Type: Bug
          Components: cvs
    Affects Versions: current
         Environment: CentOS release 5.4 64-bit, Tomcat 6.0.20, Jenkins 1.454
            Reporter: jacekw
            Priority: Blocker


On version 1.6 everything was ok. Now every job using cvs fails.

After updating cvs plugin from version 1.6 to 2.0 I get:

FATAL: CVS authentication failure while running rlog command
java.lang.RuntimeException: CVS authentication failure while running rlog 
command
        at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:529)
        at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:409)
        at hudson.scm.CVSSCM.checkout(CVSSCM.java:829)
        at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
        at 
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
        at hudson.model.Run.run(Run.java:1408)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:238)
Caused by: org.netbeans.lib.cvsclient.connection.AuthenticationException: 
Timeout, no response from server.
        at org.netbeans.lib.cvsclient.Client.ensureConnection(Client.java:418)
        at 
org.netbeans.lib.cvsclient.command.log.RlogCommand.execute(RlogCommand.java:357)
        at org.netbeans.lib.cvsclient.Client.executeCommand(Client.java:710)
        at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:521)
        ... 9 more


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to