Sowing new build as historical one
Answered
Hello
I have TC version: TeamCity Enterprise 9.1.7 (build 37573) with license for 4 agents:
I have strange situation got deploy configuration showing me not recent version of component.
Below is screen what TC is showing me when I open main project deployment for our UAT
but when I go to Deploy UAT to see historical data it showing me new ones.
How can it possible that historical build show not the right ones.
Below is the version that showing me for at main view but this is not version that was deployed recently.
Any ideas?
Piotr
Please sign in to leave a comment.
Hello Piotr,
A build that starts after a build with more recent changes is called History and not shown on Overview page. This is "by design", see https://confluence.jetbrains.com/display/TCD10/History+Build.
Do you run these build via Run custom dialog? We have the related request to allow custom builds not to be mark as history builds: https://youtrack.jetbrains.com/issue/TW-20891. Please vote for the request.
Well I am using Snapshot dependency to start build .
Really strange we got similar build configuration that is running our deploy STAGE and PROD and use same snapshot dependency mechanism and I can see proper version number.
Here is snapshot dependency:
Hello,
History builds are shown on the dependencies tabs, they are not shown on Projects or Build Configuration > Overview page. For more details please see the section: https://confluence.jetbrains.com/display/TCD10/History+Build.
Do you use quiet period or changed the order of queued builds manually?