The Tag Repository Changeset build event handler can be used to tag or label changesets in the respository when certain build events occur. You may, for example, wish to label changesets which were successfully deployed with the build version number.
Continua currently support tagging for Git, Mercurial and Subversion repositories. Continua attempts to provide a consistant interface for tagging across all of these repositories, although the implementation varies significantly.
Enter the name of the tag. You can use expressions here but ensure that the character are restricted to those allowed by the selected repository type.
A comment to be stored in the repository against the tag (for Git) or tag changeset (for Mercurial and Subversion). You can use expressions in the field.
This is one of the following:
You
You can choose to apply the tagging action to the First or Last changeset associated with the build. This is only relevant if the build is run with the "Associate all changesets since last successful build" option selected.
You can specfy when the build event handler runs by linking it to a Build Event on the When To Run tab
Select the event which triggers the tag action. You can choose one of the following Build Events:
For stage events, select the stage this applies to, or "(all stages)" to trigger the tagging action for all stages
For "On Stage Completed" and "On Build Completed", you can choose to trigger the tagging action when the build is Successful or has Failed.
Some repositories (Mercurial and Subversion) record