This page is maintained for legacy reasons and it is suggested to use GitLab for version control.
UMIACS provides a centrally managed Subversion service.
To have a Subversion repository created you need to just email staff and provide the name of your repository and how much initial space you think you will need.
By default we will configure all repositories to be private and require authentication for both reading and writing to the Subversion repository. Authentication is done against our LDAP and if requested we can enable a UMIACS user to manage the AR with our ApplicationResourceUtil found at https://intranet.umiacs.umd.edu/arutil.
Getting Started with Subversion
You will first need to check out your repository,
This will create a directory in your current working directory with the name of the last part of the URL you just checked out.
You can now add files by the svn import command, svn add can be used to add file that you have created but is not under revision control yet.
Most Linux distributions include subversion clients in the distribution including all our Red Hat Enterprise Linux clients.
Collab.net Subversion Packages
These are well packaged subversion command line packages. You can find ones for Windows, macOS and Solaris. Please see the community downloads for macOS.
Command line subversions store your password be default on linux, so you should be careful. In order to disable password caching completely, add the line: "store-passwords = no" to the subversion configuration file on your machine. In order to disable caching for a one time command you can pass the --no-auth-cache option.
Server Certificate Verification on macOS
The command-line svn tool that is bundled with macOS through Xcode does not correctly handle the UMIACS subversion server certificate. In order to verify that you are actually connecting to UMIACS, verify that the following fingerprint matches:
If this fingerprint matches, you can safely accept the certificate.