[ http://jira.codehaus.org/browse/CONTINUUM-687?page=comments#action_74678
]
David Roussel commented on CONTINUUM-687:
-----------------------------------------
The way I would imagine this working is:
- create a plugin to do the label
- configure it as shown below
- configure continuum to execute the 'label' goal
...
<plugin>
<groupId>com.mycompany.example</groupId>
<artifactId>label-maven-plugin</artifactId>
<executions>
<execution>
<phase>verify</phase>
<configuration>
<file>${project.output.directory}/buildNumber.txt</file>
</configuration>
<goals>
<goal>label</goal>
</goals>
</execution>
</executions>
</plugin>
...
See
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
for how the goal integrates to the lifecycle.
> Option to trigger the SCM system to tag successful builds with a build number
> or timestamp.
> -------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-687
> URL: http://jira.codehaus.org/browse/CONTINUUM-687
> Project: Continuum
> Issue Type: New Feature
> Components: Core system, SCM
> Reporter: Christian Gruber
>
> This is complex, because it would be different for each type. For maven2,
> for example, it would be potentially compled on its own, insofar as tagging
> is handled quite differently between CVS and SVN (to pick two). I could see
> a potential workaround, if build defs were independent within a project, by
> using a specific goal (say on a nightly build) and therefor "manually"
> invoking scm:tag or something.
> In short, I'm not sure if it's better to do this within the build system, or
> continuum. Suggestions? Best practices anyone?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
