Jump to content

Bug: TeamCity Plugin labels the wrong changeset

Olaf Kober

Recommended Posts


I'm talking about Plastic SCM 4.0.239 and the new TeamCity plugin (SNAPSHOT-201201101716), but I guess the issue existed in the v3 plugin.

Let's say a build configuration starts with changeset 1234 and while the build is running other changesets were created on the branch the build is running from. After the build finishes TeamCity automatically creates a label (you can configure this), but unfortunantely it does not label the changeset 1234, but the last changeset on the branch (Bug!!!).

Some of our TeamCity build configurations take some time (about an hour). So this can happen quite often.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...