SVN

Owned by Former user (Deleted)
Aug 04, 2014
2 min read

Add User

https://svn0.uits.uconn.edu/admin/

manage developers

Add new repository

When a developer starts a new project

go to:

https://svn0.uits.uconn.edu/admin/

add new repository

add new project in the new repository

add developers to new project in new repository

email the developer the new svn url: https://svn0.uits.uconn.edu/OrgLdapUpdate/OrgLdapUpdate/trunk

 

log in as root to svn0.uits.uconn.edu

cp /srv/svn/kuali/conf/apache.htpasswd /srv/svn/<NEW REPO>/conf
cd /srv/svn/<NEW REPO>/conf
chown www-data:www-data apache.htpasswd 
 

add a new file in /etc/apache2/custom with a name <NEW REPO>_basic.conf, with the following contents:

<Location /<NEW_REPO>_basic>
  #  Require SSL
  SSLRequireSSL On
  #  Only on-campus servers allowed
  Order allow,deny
  Allow from 137.99
  Allow from 10.91.0.40
  # Uncomment this to enable the repository
  DAV svn
  # Set this to the path to your repository
  SVNPath /srv/svn/<NEW_REPO>
  #  Successful authentication implies authenticating to
  #  both Apache and SVN
  #  Authenticating to Apache
  AuthType Basic
  AuthName "WebDev Subversion Repository Basic Auth"
  AuthUserFile /srv/svn/<NEW_REPO>/conf/apache.htpasswd
  require valid-user

  #  NOTE:  For reasons unknow, AuthzSVNAccessFile is not working
  #         with BASIC auth, but that's OK, because we are only
  #         using BASIC auth with specific servers.
  #  Authenticatign to SVN
  #  AuthzSVNAccessFile /srv/svn/kuali/conf/authz.http
  # The following three lines allow anonymous read, but make
  # committers authenticate themselves.  It requires the 'authz_user'
  # module (enable it with 'a2enmod').
  #<LimitExcept GET PROPFIND OPTIONS REPORT>
    #Require valid-user
  #</LimitExcept> 
</Location>
~

finally run 

/etc/init.d/apache2 restart

Make sure you have initially created all the projects you require in the new repository before adding the pre-commit hooks, as they can cause permissions issues. If you need to add more projects after the hooks are enabled, you can temporarily disable the hook scripts, create the projects, then re-enable them.

 

next, cd /srv/svn/<NEW REPO>/hooks

make the pre-commit file look like so:

#!/bin/sh

/usr/bin/python /srv/svn/<NEW_REPO>/hooks/jira-client.py $1 $2

Make sure it has the correct ownership and permissions

chown www-data:www-data pre-commit
chmod 755 pre-commit

then:

cp /srv/svn/kuali/hooks/jira-client.py /srv/svn/<NEW_REPO>/hooks/

then edit the /srv/svn/<NEW_REPO>/hooks/jira-client.py file like such:

# change projectKey = '*'
# to
projectKey = '<NEW_REPO_JIRA_KEY>'

make sure it has the correct ownership

chown www-data:www-data jira-client.py

 

 

(you'll usually want to create a new JIRA project as well)

(you'll also want to go to fisheye and add the new repository)

select administration from the dropdown to the right hand side of your name, this should bring up the repositories page, click add existing, use the same name as chosen in the svn admin web application, and add a description. click next, for SVN URL use the following template:

https://svn0.uits.uconn.edu/<NEW_REPO>_basic

username: jira 

password: f599519f0885

test the connection, then hit next

cog -> enable , cog -> start

now copy the 'location' url for the JIRA project

in the new JIRA project, make sure to set "repository path" from project administration settings 

Â