Difference: SubversionRepository (13 vs. 14)
Revision 142016-04-25 - GordonStewart
| Line: 1 to 1 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| Changed: | ||||||||||
| < < | Local Subversion Repository | |||||||||
| > > | Subversion | |||||||||
| Changed: | ||||||||||
| < < | A local subversion repository is being setup, when ready this page will describe how to access it. | |||||||||
| > > | PPE hosts several Subversion repositories: | |||||||||
| Changed: | ||||||||||
| < < | For more information on subversion see the Subversion book or the Subversion FAQs. | |||||||||
| > > | ||||||||||
| Changed: | ||||||||||
| < < | ||||||||||
| > > | You must have a grid certificate to access these repositories, and this must be registered with PPE IT support. | |||||||||
| Changed: | ||||||||||
| < < | Repository Organisation | |||||||||
| > > | 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. | |||||||||
| Deleted: | ||||||||||
| < < | Currently there are four subversion repositories: | |||||||||
| Changed: | ||||||||||
| < < |
| |||||||||
| > > | Using Subversion | |||||||||
| Changed: | ||||||||||
| < < | The test repository is as the name suggests for testing and getting used to using subversion. It will be cleaned out and reset on an irregular basis and without notice. | |||||||||
| > > | For a complete guide to using Subversion, please refer to Version Control with Subversion. This section contains information specific to the PPE repository configuration. | |||||||||
| Changed: | ||||||||||
| < < | NB: Browsers will often repeatedly ask for you to choose a certificate at this point. To get around this, you can (in Firefox) choose Edit >> Preferences>> Advanced and click the radio button Select one Automatically in the certificates section. | |||||||||
| > > | 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. | |||||||||
| Deleted: | ||||||||||
| < < | To request an additional repo contact the ITManagement | |||||||||
| Changed: | ||||||||||
| < < | Websvn Access | |||||||||
| > > | Creating a user or project directory | |||||||||
| Changed: | ||||||||||
| < < | The repos can also be viewed using websvn: | |||||||||
| > > | 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: | |||||||||
| Changed: | ||||||||||
| < < | ||||||||||
| > > | $ svn mkdir https://svn.ppe.gla.ac.uk/<REPOSITORY>/<DIRECTORY> -m <COMMIT MESSAGE> | |||||||||
| Changed: | ||||||||||
| < < | NB: Browsers will often repeatedly ask for you to choose a certificate at this point. To get around this, you can (in Firefox) choose Edit >> Preferences>> Advanced and click the radio button Select one Automatically in the certificates section. | |||||||||
| > > | For example, to create a directory called squirrel within the test repository: | |||||||||
| Changed: | ||||||||||
| < < | Using the repositories | |||||||||
| > > | $ svn mkdir https://svn.ppe.gla.ac.uk/test/squirrel -m "Directory for Squirrel project" | |||||||||
| Deleted: | ||||||||||
| < < | All users, once registered to access the repositories, have full read and write access to any files in any of the repositories. So please take care especially when committing changes and when setting up new directories. | |||||||||
| Changed: | ||||||||||
| < < | To help keep some order in the user repository please do not commit files into the top level repo directory. Instead create a directory named after your user name and store personal files/projects under this directory. | |||||||||
| > > | Setting up access | |||||||||
| Changed: | ||||||||||
| < < |
| |||||||||
| > > | Before you can access the Subversion repositories, you must have a grid certificate and this must be registered with PPE IT support. | |||||||||
| Changed: | ||||||||||
| < < | For organising files/projects the subversion book http://svnbook.red-bean.com/ describes some recommended possible layouts, in the section Planning Your Repository Organization. | |||||||||
| > > | 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: | |||||||||
| Changed: | ||||||||||
| < < | Setting up access | |||||||||
| > > | ppe = *.ppe.gla.ac.uk | |||||||||
| Changed: | ||||||||||
| < < | Access to the ppe subversion repository and the trac web pages is via grid certificate. Only users who have registered their certificate with the ITManagement can access to either the repository or the trac pages. To register your certificate for access to the repository email ppesysman@physics.gla.ac.uk with your certificate distinguished name (DN). This can be found with the openssl command (the example assumes your certificate is in ~/.globus/usercert.pem): | |||||||||
| > > | Next, add the following to the end of the file: | |||||||||
| Changed: | ||||||||||
| < < |
| |||||||||
| > > | ssl-client-cert-file = <PATH TO HOME DIRECTORY>/.globus/usercred.p12 ssl-authority-files = <PATH TO HOME DIRECTORY>/.globus/usercert.pem | |||||||||
| Changed: | ||||||||||
| < < | Once your certificate is registered for access no addition setup is require to access the trac pages however for access to the subversion repository additional setup is required. | |||||||||
| > > | 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: | |||||||||
| Changed: | ||||||||||
| < < | First if you do not have a .subversion directory in your home directory run svn --version to create one. | |||||||||
| > > | $ openssl pkcs12 -in usercred.p12 -nokeys -clcerts -out usercert.pem $ openssl pkcs12 -in usercred.p12 -nocerts -out userkey.pem $ chmod 600 userkey.pem | |||||||||
| Changed: | ||||||||||
| < < | Inside the .subversion directory is the file servers this file requires editing to access the repository. Edit the groups section of the file adding the line: | |||||||||
| > > | You can check that you have configured things correctly by listing the contents of one of the repositories: | |||||||||
| Changed: | ||||||||||
| < < | ppe = *.ppe.gla.ac.uk | |||||||||
| > > | $ svn list https://svn.ppe.gla.ac.uk/test | |||||||||
| Deleted: | ||||||||||
| < < | to create a ppe group. It should look something like: | |||||||||
| Changed: | ||||||||||
| < < | [groups] # group1 = *.collab.net # othergroup = repository.blarggitywhoomph.com # thirdgroup = *.example.com ppe = *.ppe.gla.ac.uk | |||||||||
| > > | E-mail notification of commits | |||||||||
| Changed: | ||||||||||
| < < | note the [groups] line may need uncommenting by removing any leading #'s. Then add the following to the end of the servers file:
[ppe] ssl-client-cert-file = /home/user_name/.globus/usercred.p12 ssl-authority-files = /home/user_name/.globus/usercert.pemReplacing user_name as appropriate. This assumes who have the pkcs12 version of your certificate in /home/user_name/.globus/usercred.p12 and a x509 format copy of your certificate in /home/user_name/.globus/usercert.pem. Access to the subversion repository requires both.
To convert a pkcs12 certificate into a pem format certificate/key file pair, use openssl:
chmod 600 userkey.pem. Note the password used to encrypt the userkey.pem file should be a strong one, this file is the private key for your grid certificate.
Then place userkey.pem and usercert.pem and usercred.p12 in ~/.globus/
Access to the repository can be tested using:
Using a proxy certificate to access the repositoryTo avoid having to type a password in each time the repository is accessed a proxy certificate can be used. In order to do this the certificate pointed to in the~/.subversion/servers file must be changed from:
ssl-client-cert-file = /home/user_name/.globus/usercred.p12to: ssl-client-cert-file = /tmp/pkcs12up_uXXXXreplacing XXXX with the output of the command id -u.
To create a proxy certificate first source grid-env.sh (or grid-env.csh, see GridServices) and then create the proxy using svn-grid-proxy-init
Setting up access with UbuntuIt is possible that trying to use SVN with Ubuntu can give you the error messagesvn: OPTIONS of 'https://ppesvn.physics.gla.ac.uk/svn/test': Could not read status line: SSL error: Key usage violation in certificate has been detected. (https://ppesvn.physics.gla.ac.uk)If this is the case, it might be something to do with having too recent a version of subversion compared to what is used in SL. The fix (that worked for me) was found here .
Email notification of commitsTo setup automatic email notification of commits create a file called!email-notify-list.svn containing a list of email addresses (one email address per line) in the subversion repository. When any changes are made to files in the directory containing !email-notify-list.svn or in any directory below this directory an email will sent out automatically to the email addresses listed in !email-notify-list.svn file. If the project layout follows the suggested subversion layout of branches, tags and trunk directories then the !email-notify-list.svn file should go in the same directory as the branch, tags and trunk directories. eg:
project_name/!email-notify-list.svn project_name/branches project_name/tags project_name/trunkMultiple !email.notify.list.svn files are also possible for example:
project_name/!email-notify-list.svn project_name/branches project_name/tags project_name/trunk project_name/trunk/!email-notify-list.svnpeople listed in project_name/!email-notify-list.svn will be notified of all changes made to the project and people listed in project_name/trunk/!email-notify-list.svn will only be notified when changes are made in project_name/trunk/ and below.
Notes:
| |||||||||
| > > | 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. | |||||||||
| ||||||||||
View topic | History: r14 < r13 < r12 < r11 | More topic actions...
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback