[
https://issues.jenkins-ci.org/browse/JENKINS-12595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Clarke resolved JENKINS-12595.
--------------------------------------
Fix Version/s: current
Resolution: Fixed
Fixed in 2.1. Caused by the checkout/update command not explicitly specifying
which module to checkout which some CVS servers didn't like
> Anonymous cvs update doesn't work anymore
> -----------------------------------------
>
> Key: JENKINS-12595
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12595
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Affects Versions: current
> Environment: CentOS 5.7, cvs-1.11.22-9.el5, cvs plugin version 2.0
> Reporter: Simon Matter
> Assignee: Michael Clarke
> Priority: Blocker
> Fix For: current
>
>
> Since the update to the java cvs plugin, I can't do anonymous readonly cvs
> update anymore. It fails with this message:
> cvs update: Updating .
> cvs update: failed to create lock directory for `/var/cvs'
> (/var/cvs/#cvs.lock): Permission denied
> cvs update: failed to obtain dir lock in repository `/var/cvs'
> cvs [update aborted]: read lock failed - giving up
> Note: Initial checkout after cleaning workspace works, only updates don't
> work.
> The is also another problem which may be a side effect: I see hanging around
> cvs server processes which only terminate after jenkins is shut down.
> We are running cvs pserver from xinetd like this: cvs -f
> --allow-root=/var/cvs pserver
> CVSROOT is ":pserver:anonymous@cvs:/var/cvs"
> Anonymous readonly updates have always worked with jenkins, as well es they
> do with Eclipse or Netbeans.
> Did I miss something?
> Regards,
> Simon
--
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
