Subversion

PPE hosts several Subversion repositories:

Repository	Link	WebSVN Link
atlas	https://svn.ppe.gla.ac.uk/atlas	https://websvn.ppe.gla.ac.uk/wsvn/atlas
lhcb	https://svn.ppe.gla.ac.uk/lhcb	https://websvn.ppe.gla.ac.uk/wsvn/lhcb
test	https://svn.ppe.gla.ac.uk/test	https://websvn.ppe.gla.ac.uk/wsvn/test
user	https://svn.ppe.gla.ac.uk/user	https://websvn.ppe.gla.ac.uk/wsvn/user

You must have a grid certificate to access these repositories, and this must be registered with PPE IT support.

In addition to our Subversion repositories, which have seen little use over the last couple of years, PPE also hosts revision control systems such as GitLab for specific projects. If you would like to discuss more up-to-date methods of revision control such as GitLab, either as an individual or for your project, please contact PPE IT support.

Using Subversion

For a complete guide to using Subversion, please refer to Version Control with Subversion. This section contains information specific to the PPE repository configuration.

Once you have registered for access, you will be granted full read and write access to all files in all repositories. Please take extreme care when committing changes not to unintentionally overwrite changes made by other users.

Creating a user or project directory

To keep the repositories organised, please do not commit files directly into the top level directory. Instead, create a directory named after your user or project, and store files under this directory:

$ svn mkdir https://svn.ppe.gla.ac.uk/<REPOSITORY>/<DIRECTORY> -m <COMMIT MESSAGE>

For example, to create a directory called squirrel within the test repository:

$ svn mkdir https://svn.ppe.gla.ac.uk/test/squirrel -m "Directory for Squirrel project"

Setting up access

Before you can access the Subversion repositories, you must have a grid certificate and this must be registered with PPE IT support.

To configure the svn command to use your certificate, open the file ~/.subversion/servers in a text editor (run svn --version if it doesn't already exist). Add the following to the [groups] section:

ppe = *.ppe.gla.ac.uk

Next, add the following to the end of the file:

ssl-client-cert-file = <PATH TO HOME DIRECTORY>/.globus/usercred.p12
ssl-authority-files = <PATH TO HOME DIRECTORY>/.globus/usercert.pem

This assumes that you have your certificate in both PKCS #12 and PEM format in the files usercred.p12 and usercert.pem respectively. Access to Subversion requires both these files. To convert a PKCS #12 file into PEM format, use the openssl command. For example, if the PKCS #12 file were named usercred.p12, you would use the following commands:

$ openssl pkcs12 -in usercred.p12 -nokeys -clcerts -out usercert.pem
$ openssl pkcs12 -in usercred.p12 -nocerts -out userkey.pem
$ chmod 600 userkey.pem

You can check that you have configured things correctly by listing the contents of one of the repositories:

$ svn list https://svn.ppe.gla.ac.uk/test

E-mail notification of commits

You can configure Subversion to notify you by e-mail when changes are committed to the repository. To do this, create a file called !email-notify-list.svn within the repository, containing the e-mail addresses (one per line) to be notified. A notification will be sent whenever a file in the same directory as !email-notify-list.svn, or in any subdirectory of the directory containing !email-notify-list.svn, is changed.