"History Build" Scenario

Answered

Here's the scenario: Setting up a new build configuration, used for deploying artifacts, had a snapshot dependency and part of a build chain. It was determined that this new build configuration should not be part of the build chain and a separate process, so the dependency removed. Future executions now say "History Build" because of the previous history (the same build configuration used to belong to the build chain). 

I had to remove all of the previous build history for the configuration in order for new runs to not be "history builds."

Seems to me that once a build configuration is updated to not be part of the build chain, that I could keep the history, and future runs of it would no longer be part of the old build chain. Bug?

8 comments
Comment actions Permalink

Hi, I'm having the same issue. Are there any solutions to this which don't purge the build history? Or is there anything we can do to help identify the root cause of this?

1
Comment actions Permalink

Hello Ed,

A History Build is a build that starts after a build with more recent changes The build can become history in the following situations: https://confluence.jetbrains.com/display/TCD10/History+Build. It should not depend on configured dependencies. 

0
Comment actions Permalink

Hi Alina... I do appreciate your response. I am familiar with how history builds work (having used TeamCity for over 10 years now), but in this case the relation to other build configurations no longer exists once the snapshot dependency is removed. In order for correct/expected functionality, all historical runs of the mis-configured build configuration must be purged. But I really would like to keep the history of the each run -- even with the mis-configuration. 

What the docs do not mention is that if changes are made and a snapshot dependency is removed after even one run, it will maintain run history and still treat every future run as history, even though it currently does not meet any of the requirements set in the situation(s) outlined.

 

0
Comment actions Permalink

Hi Ed,

What VCS roots do you have configured in both build configurations? I tried to reproduce the issue but with no success. Could you please provide a minimum number of steps to reproduce this?

 
0
Comment actions Permalink

In this case, none of them use VCS Roots. We're using TeamCity as a dashboard for deploying artifacts to various environments (in front of an OctopusDeploy Server). Yes, I know it's a bit overkill, but the real-world situation is that users just want one place to go for everything. 

I didn't know you were going to try to repo the problem...THANKS! I will spend some time and document my setup very soon.

0
Comment actions Permalink

Hi, I am struggling with same issue where my build were having snapshots dependency before and now after removing them all new builds are showing as history builds. Did you guys have any solution for same? thanks in advance.

0
Comment actions Permalink

Is there a way to determine what dependency or VCS root is being deemed "newer" in order to know why a build is considered a history build?

0
Comment actions Permalink

Hi Larry,

it's not directly possible to see which is being deemed "newer", but:
-Dependencies being removed is a bug that was fixed already and shouldn't happen on recent versions. Other than that, you could store the project settings in version control in order to track which changes have happened and then you can correlate where the history builds start and what happened.
-Under the "Changes" column, you can see which revisions have been selected for the build. While not explicit, you might, again, be able to correlate older revisions and newer missing to trace which were failing.

0

Please sign in to leave a comment.