Team City 4.0 supports relative URL in the svn:externals property of Subversion 1.5

In my September post, I wrote that we upgraded our development environment from Subversion 1.4 to Subversion 1.5. We were hoping to use relative URL's in svn:externals property - the feature introduced in Subversion 1.5. We use svn:externals to connect to shared non-compilable release units, such as common styles, images, script libraries, content, etc. We immediately found out that although Team City 3.2, our build and integration server at the time, supported Subversion 1.5, it did not recognize relative URL's in svn:externals. We have recently upgraded our build server to Team City 4.0 and it does support relative URL's in svn:externals!

Contact me if you have any questions on how to structure your Subversion repository. Happy coding!

From Subversion 1.4 to Subversion 1.5

Last week, we upgraded our development environment from Subversion 1.4 running on Apache 2.0 to Subversion 1.5 running on Apache 2.2. The primary reason for this upgrade is the support of relative URLs in the svn:externals property introduced in the new version of Subversion. 

The upgrade process was smooth and easy. Here are the steps we followed:   

  1. Stopped our existing Apache Server
  2. Backed up our Subversion repository 
  3. Downloaded and installed Apache 2.2.9
  4. Downloaded and installed Subverstion 1.5.2
  5. Configured httpd.conf configuration file for our new Apache server and started the server
  6. Upgraded our repository by executing svnadmin upgrade
  7. Upgraded our indexes by executing svn-populate-node-origins-index
  8. Upgraded client tools - we installed Tortoise 1.5.3 and Ankh 2.0
  9. Upgraded Team City automated build and continuous integration server to the latest version 3.1.2
A couple of notes... 
  • In the past, in order to use Windows authentication with Subversion we had to write a custom We did not have to do anything for 1.5. Loading modules in the correct order and referencing them from the Subversion application folder did the trick for us:     
LoadModule sspi_auth_module modules/
LoadModule dav_module modules/
LoadModule dav_svn_module C:/Apps/svn-win32-1.5.2/bin/
LoadModule authz_svn_module C:/Apps/svn-win32-1.5.2/bin/               
<Location /svn>
DAV svn
SVNPath C:\Dev\Repository

     AuthName "SVN Server"
     AuthType SSPI
     SSPIAuth On
     SSPIAuthoritative On
AuthzSVNAccessFile "C:/Repository/conf/authz"
     SSPIOfferBasic on
     Require valid-user     

  • Team City 3.1.2 does support Subversion 1.5, but unfortunately does not support relative URL's in the svn:externals property. 

Welcome to ModelBlog

Thank you for visiting ModelBlog. We hope the time you spend with us will be both entertaining and worth your while. Have fun!