False History builds in build configuration

I have a chain of build configurations linked together through snapshot dependencies:

Trigger -> BuildIOS -> BuildAndDeploy -> ...

The Trigger config is triggered by VCS changes and monitors a number of branches. BuildIOS is triggered on a successful build in Trigger, and BuildAndDeploy is triggered on a successful build in BuildIOS.

Yesterday I had a situation where builds were failing due to a bug in an external component responsible for running tests. As a result, I ended up running the Trigger config manually a few times. Eventually, I managed to downgrade the external component and got a successful build through.

Now I have two related problems:

1. The dashboard only shows the first failing build of BuildAndDeploy, not the last successful. In the attached screenshot, tc-dashboard.png, it's build 2.0.1.797 in the master branch.

2. The last few builds under BuildAndDeploy are marked as History builds (I suppose this is the reason for 1). See the attached screenshot tc-history.png.

So my question: How do I make TeamCity understand that the builds are not History builds? The Trigger build config does not show the manually triggered builds as History builds.

Thanks,
Per



Attachment(s):
tc-history.png
tc-dashboard.png
1 comment
Comment actions Permalink

Never mind, the problem was a bug in my build script that prevented the build number from being communicated to TeamCity via a service message...

0

Please sign in to leave a comment.