Website:Subversion

From UGCS
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 +
==User Documentation==
 +
* If you don't have it already, create ~/public/svn. and type: fs sa ~/public/svn svn rlidwka
 +
* Anything in ~/public/svn will be accessible at svn://svn.ugcs.caltech.edu/USERNAME. You can also use svn://svn.ugcs.net/USERNAME. A tilde before the username is optional but not required.
 +
* To create a new repository in less than two minutes:
 +
** type: cd ~/public/svn
 +
** type: svnadmin create REPOSITORYNAME
 +
** type: cd REPOSITORYNAME/conf
 +
** edit the file passwd. At the bottom, in the users section, add one line per person who needs to be able to access the server. Each line is formatted like USERNAME=PASSWORD.
 +
** edit the file svnserve.conf. Add the following under the [general] section:
 +
*** anon-access = none # Can also be read or write to let anyone in the world perform that op.
 +
*** auth-access = write # Can also be read or none to control what users in the passwd file can do. Write permission implies read permission
 +
*** password-db = passwd
 +
** Done! You can access your new repository at svn://svn.ugcs.caltech.edu/USERNAME/REPOSITORYNAME
 +
** Note: You will need to add an entry for yourself in the passwd file as well, it is NOT the same as your ugcs password. DO NOT REUSE YOUR UGCS PASSWORD! Since you only have to enter the svn password once, the first time you access the repository on a given machine, choose something strong; you can always check the passwd file if you forget.
 +
 +
==Bugs/Issues==
 +
===Presumed Fixed===
 +
* Initially, sometimes after doing checkout / restart svn / make change / checkin / restart /checkout and similar sets of steps, some files in the user's volume will begin getting permission denied errors. This will occur when accessed as the user or as svn, but only on poseidon, on other hosts it behaves normally. You can fix it by renaming the offending files (on poseidon or elsewhere) the naming them back.
 +
** Since we went to separate process svnserve instead of threaded, and added kdestroy and unlog in the stop script, this has not recurred to my knowledge.
 +
*** Began having these issues again. I added in instructions to flush all svn-using users' volumes on svn start, which appears to fix the problem. As in, I was able to reliably recreate it, did this, and now can no longer get it at all.
 +
* Despite instructions to the contrary in kadmin and in the init script, svn will eventually get permission denied errors. This is presumed due to ticket expiration. I have added a daily restart to svnserve once per day to poseidon's crontab. A better fix would be nice but this should do for now.
 +
 +
-------------------
 +
 
=Subversion=
 
=Subversion=
  

Revision as of 04:51, 16 February 2009

Contents

User Documentation

  • If you don't have it already, create ~/public/svn. and type: fs sa ~/public/svn svn rlidwka
  • Anything in ~/public/svn will be accessible at svn://svn.ugcs.caltech.edu/USERNAME. You can also use svn://svn.ugcs.net/USERNAME. A tilde before the username is optional but not required.
  • To create a new repository in less than two minutes:
    • type: cd ~/public/svn
    • type: svnadmin create REPOSITORYNAME
    • type: cd REPOSITORYNAME/conf
    • edit the file passwd. At the bottom, in the users section, add one line per person who needs to be able to access the server. Each line is formatted like USERNAME=PASSWORD.
    • edit the file svnserve.conf. Add the following under the [general] section:
      • anon-access = none # Can also be read or write to let anyone in the world perform that op.
      • auth-access = write # Can also be read or none to control what users in the passwd file can do. Write permission implies read permission
      • password-db = passwd
    • Done! You can access your new repository at svn://svn.ugcs.caltech.edu/USERNAME/REPOSITORYNAME
    • Note: You will need to add an entry for yourself in the passwd file as well, it is NOT the same as your ugcs password. DO NOT REUSE YOUR UGCS PASSWORD! Since you only have to enter the svn password once, the first time you access the repository on a given machine, choose something strong; you can always check the passwd file if you forget.

Bugs/Issues

Presumed Fixed

  • Initially, sometimes after doing checkout / restart svn / make change / checkin / restart /checkout and similar sets of steps, some files in the user's volume will begin getting permission denied errors. This will occur when accessed as the user or as svn, but only on poseidon, on other hosts it behaves normally. You can fix it by renaming the offending files (on poseidon or elsewhere) the naming them back.
    • Since we went to separate process svnserve instead of threaded, and added kdestroy and unlog in the stop script, this has not recurred to my knowledge.
      • Began having these issues again. I added in instructions to flush all svn-using users' volumes on svn start, which appears to fix the problem. As in, I was able to reliably recreate it, did this, and now can no longer get it at all.
  • Despite instructions to the contrary in kadmin and in the init script, svn will eventually get permission denied errors. This is presumed due to ticket expiration. I have added a daily restart to svnserve once per day to poseidon's crontab. A better fix would be nice but this should do for now.

Subversion

Please note: this is not an introduction/howto for Subversion in general; you should google for that. This is how to set up and begin using a Subversion repository on the UGCS cluster.

To create a svn repository, run this on the cluster: 

svnadmin create ~/public/svn

By default, anyone will be able to check out the code but only you will be able to edit it. In order to allow others to edit it you will need to grant them rlidw permissions, and in order to allow others to read it you will need to grant them rl permissions. To make a repository private, do not give anyone any other privileges (eg by creating in your ~ instead of in public).

To change permissions on your repository, see AFS ACLs

eg, to let anyone check in or out code: 

fs sa ~/public/svn system:authuser rlidw

Once you have created a repository, you can access it from any computer as follows: 

svn co svn+ssh://calliope.ugcs.caltech.edu/afs/.ugcs/user/<username>/public/svn

replacing co with whatever SVN operation you want, and the path above with the path to your repository

Retrieved from "http://www.ugcs.caltech.edu/wiki/Website:Subversion"
Personal tools