[
https://issues.jenkins-ci.org/browse/JENKINS-12595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158572#comment-158572
]
Simon Matter commented on JENKINS-12595:
----------------------------------------
I've tried quite a lot but just couldn't find what is wrong.
The jenkins user doesn't matter at all because we are running over the network
with pserver, so directory access of the jenkins user has no effect.
The 'anonymous' user is mapped to unix user 'anoncvs' on the cvs server, which
has no password in $CVSROOT/CVSROOT/passwd and is member of the unix group
'cvs', which has write access into the cvs modules directories. Of course
'anonymous' is also listed in $CVSROOT/CVSROOT/readers
Both, 'cvs' and 'anoncvs' have no write permission on directory $CVSROOT
(/var/cvs), which is owned by root. The only access they have is to the
subdirectories of /var/cvs. Like this:
drwxr-xr-x 5 root root 4096 Jan 31 07:18 /var/cvs
drwxrwxr-x 3 cvs cvs 4096 Feb 3 08:52 /var/cvs/CVSROOT
drwxrwxr-x 7 cvs cvs 4096 Feb 3 08:07 /var/cvs/invoca
The main question is, why does the cvs update try to create a lock for
`/var/cvs' (/var/cvs/#cvs.lock) which is the repository root? That makes no
sense and is not allowed.
Can it be that the problem is relatd to the new feature that multiple modules
can be handled together? To me it seems that the list of directories to update
from cvs also includes the repository root, which it should not.
Thanks for looking into it,
Simon
> 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
> Priority: Blocker
>
> 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
