Question

I maintain the build system at my company, which is currently using CVS. This build system is used across multiple projects and multiple CVS repositories.

Whenever we have a release milestone, we create a tag. In CVS, this is easy:

$ cvs tag TAG_NAME 

That command works regardless of the CVS module or repository, as long as it is executed in a CVS working directory.

In order to do the same thing in subversion though, it looks like I will first have to parse the output of svn info to get the repository root. Then I can create the tag with:

svn cp . $REPO_ROOT/tags/TAG_NAME -m'Created tag TAG_NAME' 

This of course assumes that the svn repository has the recommended ‘trunk, tags, branches’ directory structure. So to be safe I’ll probably need to verify this first.

That seems like a lot of work just to map a revision number to a symbolic name. Is there a better way?

Answer 1

Here is how I implemented this, in case anyone is curious:

<!-- First, we need to get the svn repository root URL by parsing the output of 'svn info'. --> <exec executable='svn' failonerror='yes'>     <arg line='info'/>      <redirector outputproperty='svninfo.out' errorproperty='svninfo.err'>         <outputfilterchain>             <linecontains>                 <contains value='Repository Root: '/>             </linecontains>              <tokenfilter>                 <replacestring from='Repository Root: ' to=''/>             </tokenfilter>         </outputfilterchain>     </redirector> </exec>  <echo level='verbose' message='Root from svn info: ${svninfo.out}'/>  <!-- Set the svn.root property from the svn info output, and append the module prefix if it exists. The module prefix allows multiple projects to use the same repository root. --> <condition property='svn.root' value='${svninfo.out}/${svn.module.prefix}'>     <isset property='svn.module.prefix'/> </condition> <!-- Note that the next line will have no effect if the property was set in the condition above, since ant properties are immutable. The effect is an 'else', if the condition above is NOT true. --> <property name='svn.root' value='${svninfo.out}'/> <echo level='verbose' message='Root: ${svn.root}'/>  <!-- Verify the tags directory exists. --> <exec executable='svn'       failonerror='no'       outputproperty='null'       errorproperty='svn.ls.error'>     <arg line='ls ${svn.root}/tags'/> </exec> <fail> Cannot find 'tags' subdirectory.  ${svn.ls.error}  The subversion repository is expected to have 'trunk', 'branches', and 'tags' subdirectories. The tag '${tag}' will need to be manually created.     <condition>         <not>             <equals arg1='${svn.ls.error}' arg2='' trim='yes'/>         </not>     </condition> </fail>  <!-- Finally, do the actual tag (copy in subversion). --> <exec executable='svn' failonerror='yes'>     <arg line='cp . ${svn.root}/tags/${tag} -m 'Created tag ${tag}''/> </exec> 

I also want to point out that I am aware of the differences between CVS and subversion with respect to tagging, and that the subversion revision is, for all practical purposes, equivalent to the tag. Unfortunately, that is not really relevant; my users want a symbolic name composed of the module name and a (different) version number.