Which version of the cvs plugin are you using? Thanks Michael
On 21 Mar 2013, at 13:43, Jens Schweikhardt <[email protected]> wrote: > I just started setting up jenkins 1.506 on CentOS 5.9 as described on > https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions > > I've configured it to checkout from our CVS repo via pserver and > CVSROOT=:pserver:jenkins@host:/repodir. However, when I look at the > checked out tree in the workspace, files have permissions 666 or 777 > (world writable, ugh!) and directories have permissions 755. > > I have already tried the following with no effect: > > * Added umask 002 early in /etc/init.d/jenkins and restarted jenkins > * Added umask 002 to Build->Execute Shell (pointless because this is > run after checkout; even without this, displaying the umask shows 002, > which is proper, but for some reason not applied during CVS checkout) > * Added CVSUMASK=002 to Configure System->Global Properties- >> Environment Variables and restarted jenkins > > Everything has proper permissions when checked out manually by > developers, even without anyone using CVSUMASK. I'm stumped. Someone > please hit me with the clue bat. > > Regards, > Jens > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
