DoIT Shared Version Control - code.doit.wisc.edu (subversion) FAQ
These are frequently asked questions regarding the shared version control system hosted at code.doit.wisc.edu
NOTE: DoIT's SVN repository is planned for shutdown this fall, please consider git.doit.wisc.edu in place of it.
From UW Madison Campus IPs
The Subversion repositories do not use your NetID password to authenticate because of security concerns with clients that don't encrypt cached passwords, convenience for users that want or need to have their client cache their password, and to allow for non-NetID access to repositories.
In place of your password, we will generate a secure random token that you will use to authenticate to your Subversion repositories. Since this token will only gain access to your Subversion repositories, you can feel safe in letting your Subversion client cache the token. However, if you work in a shared environment where non-project-collaborators will be able to view your home directory, then you should configure your client to not cache the token.
Create it yourself here: https://code.doit.wisc.edu/
You can create groups and assign permissions here: https://code.doit.wisc.edu/
Any member of the 'owners' group of your repository can administer it. Initially the person who creates the repository is the only member of the owners group. An owner can add other members to the owners group.
Yes. Role accounts can be used for scripted access to your repository, or if you need to allow non-NetID user access.
Yes. Be careful not to expose sensitive information.
Nightly subversion repository dumps which are then backed up using Bucky Backup
Yes, e-mail us.
Yes, e-mail us.
Repository names are global in scope, so please pick a name appropriately. For example, don't call your repository "cms"; instead call it "mydepartment-cms".
What, like your personal MP3 collection? Don't do that.
Be reasonable. Keep your code, configs, and even some static content (web images). Don't keep tarballs, installers or other large files if you can avoid it.
Also, avoid storing sensitive information like keys and passwords. Even if you don't give anonymous access to that part of your repository, you still need to be careful if you work in a shared environment.
The default directory permission gives the 'owners' group read and write access to '/'. Anonymous access is denied. Permissions are inherited.
If you are browsing your repository from your web browser (e.g. https://code.doit.wisc.edu/svn/nameofrepository/...) you cannot log out. The only way to log out is to close your browser. The reason for this is because browsers do not support logout of Basic Auth (http://httpd.apache.org/docs/1.3/howto/auth.html#logout).
Of course, you can log out of the administrative application (https://code.doit.wisc.edu/manage) since it uses NetID Login (pubcookie).
Sure, just create one in our test environment here: https://code-dev.doit.wisc.edu
Email notifications is the most common hook script, and that hook script is built in to all repositories. If you would like to implement a custom hook script, then we have built in the ability for the subversion server to execute a hook script that is running as a web application on your server.
Are there any utility scripts or tools available to help me manage my repository or my change management process?
It helps a fish see things, and it's also the name of a software application that helps you browse your repository. FishEye is available to all. More here: http://www.atlassian.com/software/fisheye/
It's the name of a software application that helps with peer reviews of code. Crucible is available to all. More here: http://www.atlassian.com/software/crucible/
Run svn from the terminal (svn list <repository URL>). It then allows the certificate to be saved and svnX will work after that.
Please e-mail us.