- IMHO, the act of checking code out, building and then labelling is not part of the typical developers build lifecycle (ie. on a single developers machine, he handles this kind of thing manually if needs be, by updating his codebase, labelling, and branching when required), this kind of automation is needed particularly when doing continuous integration.
- The release plugin could do the job but when does it run, where is it configured ? - If I call the scm:tag command as part of a shell script integration in continuum, surely its build cycle is independent of the original project and hence may be inconsistent. Somehow the entire build cycle for a given project should be a single unit of work, all the way from checkout, build, test, and then potentially apply a label. Ahmed -- View this message in context: http://www.nabble.com/Listeners-for-build-events-tf1923745.html#a5272261 Sent from the Continuum - Dev forum at Nabble.com.
