On 7/11/06, Ahmed Omarjee <[EMAIL PROTECTED]> wrote:
Some questions: - Should the continuous integration tool not take the responsibility for performing the labelling, since it checked out the code, reports and notifies interested parties on success or failure of the compilation and tests against that code ?
Not neccessary, IMO since it already has some other mean to do it - In my mind the fact that I have built and run my tests successfully does
not necessarily equate to me making a release. Any thoughts ?
behind the scene, release plugin, in general, label the source, validate the build. It can be reused for other purposes where label is required for each build. - Lastly, how can I automate the act of labelling if this is not part of the
continuous build process?
Create continuum shell project and configure this command to run mvn scm:tag -Dtag=sometag scm:bootstrap -Dgoals=install never try it thou You may need to write a custom plugin to automate the tagname generation. Ahmed
http://www.nabble.com/forum/ViewPost.jtp?post=2736062&framed=y -- View this message in context: http://www.nabble.com/Listeners-for-build-events-tf1923745.html#a5271292 Sent from the Continuum - Dev forum at Nabble.com.
