svn:externals & tagging, how to combine code between teams
From: Charles Chan <cchan_qa_at_yahoo.com>
Date: Fri, 29 Jan 2010 20:12:18 -0800 (PST)
In our company, we are working on a product composed of different C/C++ modules. Ideally, each tier and module should be developed by separately by different teams and tested independently. Currently, we have separate each module into it's own branch:\
The modules are:
Separately, the product release is build by combining the modules and compiled regularly using a CI system.
The main problem we are having is with the behavior of 'svn tag' in association with externs. The current externs are referencing the HEAD -- because we would like to build the latest version regularly to ensure all modules works together. However, once a build is successful and we proceed to make a release, it would be nice if there was an easy way to automatically tag everything -- including the version used in the extern. As it stands today, we have to create tags for the modules and then update the externs to these tags, then tag the product, and finally swap it back to the trunk after.
Is there a cleaner way to do this? Feel free to also comment on the current structure.
This is an archived mail posted to the Subversion Users mailing list.