Adding automatic tagging of the repository after each successful continuous
build
---------------------------------------------------------------------------------
Key: MISC-38
URL: http://jira.andromda.org/browse/MISC-38
Project: Miscellaneous
Type: New Feature
Reporter: Cédric Vidal
Assigned to: Wouter Zoons
Today it's really hard to get a source version that match a binary one.
I'm personaly interested in snaphot versions from
http://team.andromda.org/maven2/, but I think that being able to match source
version to binary ones would be of interest to the whole AndroMDA community.
Would you mind tagging the repository after each successful build (which gets
deployed of course).
I believe this shouldn't be difficult since you seem to use CruiseControl to
manage your builds, and as far as I remember (I've not used CC for a while)
CruiseControl exposes the exact checkout timestamp information. You could use
that information in order to tag the repository with the release version
against the exact checkout timestamp.
That way it would be possible to replay a specific build, to remote debug a
specific release or snapshot version and to be able to visualise the sources
(in eclipse for example) when developing an extension to AndroMDA.
For example, for andromda-3.2-RC1-20051214.001524-1.pom you could use the
following tags:
CC_ANDROMDA_3_2_RC1_20051214_001524_1
CC_ANDROMDA_3_2_RC1_SNAPSHOT
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
