Getting Tag-Informations from BuildChangeset does not work

[rynardald (Albrecht Hultsch)]

Hi,
I have a git repository which is configured to detect and list new tags and a trigger which triggers a build on a new tag. This works fine, but when i try to get some information’s about the triggering tag it returns no data anymore. Before it works, it must be broken in one of the last updates. I’m working with the current version of ContinuaCI (1.9.0.244).

Especially following expressions does not work:
$Source.REPO.BuiltChangeset.FirstTagName$
$Source.REPO.BuiltChangeset.LatestTagName$
$Source.REPO.BuiltChangeset.TagNames$

One which works was:
$Source.REPO.BuiltChangeset.ChangedTagName$

[Sparky (Dave Sparks)]

Hi Albrecht,

When “Detect and list as new changeset” is selected for the Tag Changes field for a Git repository, and a new tag is detected when polling the repository, Continua CI creates a new changeset in the database to represent the tag addition. This changeset references the same source files as the tagged changeset. You can see this changeset listed in the Changes tag of the Configuration view.

The tag change changeset here with the comment “Inserted lightweight tag ‘tag1’” does not have any tags on it so its FirstTagName, LatestTagName and TagNames properties are empty. Its ChangedTagName property does however have the name of the tag which was added.

The changeset here with the comment “Initial commit” is the changeset which the tag is applied to. It has a tag on it so the FirstTagName, LatestTagName and TagNames properties will include the tag name ‘tag1’. The ChangedTagName property is empty on this changeset.

When a repository trigger is set to trigger on tag changes, it triggers a build on the tag change changeset with the comment “Inserted lightweight tag ‘tag1’”. By default, Continua CI then builds this changeset and therefore $Source.Repo.BuiltChangeset$ points to the tag change changeset. This is why the FirstTagName, LatestTagName and TagNames properties of $Source.Repo.BuiltChangeset$ are empty.

In the trigger settings, under the Tags tab, there is an option “Build tagged changeset”.

If this is ticked, then the changeset that the tag is added (e.g. with the comment “Initial commit”) to e.g. is built as you can see below.

In this case, the FirstTagName, LatestTagName and TagNames properties of $Source.Repo.BuiltChangeset$ will contain “Tag1” and the ChangedTagName property will be empty.