You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Gruber (JIRA)" <ji...@codehaus.org> on 2006/05/08 18:38:41 UTC
[jira] Created: (CONTINUUM-687) Option to trigger the SCM system to
tag successful builds with a build number or timestamp.
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
Type: New Feature
Components: Core system
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
[jira] Updated: (CONTINUUM-687) Option to trigger the SCM system to
tag successful builds with a build number or timestamp.
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-687?page=all ]
Emmanuel Venisse updated CONTINUUM-687:
---------------------------------------
Component: SCM
> 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
> Type: New Feature
> Components: SCM, Core system
> 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
[jira] Commented: (CONTINUUM-687) Option to trigger the SCM system
to tag successful builds with a build number or timestamp.
Posted by "David Roussel (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (CONTINUUM-687) Option to trigger the SCM system to
tag successful builds with a build number or timestamp.
Posted by "Jesse McConnell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse McConnell updated CONTINUUM-687:
--------------------------------------
Fix Version/s: Future
> 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
> Fix For: Future
>
>
> 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
[jira] Commented: (CONTINUUM-687) Option to trigger the SCM system
to tag successful builds with a build number or timestamp.
Posted by "Sharmarke Aden (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-687?page=comments#action_65214 ]
Sharmarke Aden commented on CONTINUUM-687:
------------------------------------------
Since there are quite a number of continuous integration systems and project management systems out there you can't really pick a particular method and expect that to fly with everyone. Ideally what you want is to have some kind of protocol that's understood by everyone that passes a build number from the continuous integration system to the project management and leave it up to the project management system to do the actually work of tagging.
In the case of Maven2, it's probably best to make the build number available to POM via a variable. I image that would be useful to people using ant as well.
> 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
> Type: New Feature
> Components: Core system
> 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
[jira] Commented: (CONTINUUM-687) Option to trigger the SCM system
to tag successful builds with a build number or timestamp.
Posted by "Roald Bankras (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-687?page=comments#action_74740 ]
Roald Bankras commented on CONTINUUM-687:
-----------------------------------------
the labeling can already be done by calling the scm plugin with goal tag.
The problem lies in the fact that continuum doesn't pass the build-nummer to maven.
> 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