Teamcity 10.0.5 broken build chain branch
Continue this message:
https://teamcity-support.jetbrains.com/hc/en-us/community/posts/205409690/comments/360000148179
3 VCS git. 1 VCS = 1 build. All VCS contain master as default. All VCS contain rc_bug. All VCS different only fetch url and name.
test3 add to build chain last. After 5-6 build.
All chain triggered VCS.
test3 did not capture the last change.
Please sign in to leave a comment.
Vcs settings
Depends settings
to reproduce the error, I can make commits in the master test1 and rc_bug test3 at the same time. I get the same situation.
Trigger setup:
Hi,
thanks for sharing the screenshots and information. From them, it seems like the builds are actually being reused, it's not that they are being picked from being new. This might happen in a situation where TeamCity detects that the default branch build contains the same information than the branch build (because the 3 VCS roots are different, this might be true). A possibility here would be to force new builds on the branches instead of reusing them.
If that's not the case, as my colleague already mentioned in your other thread, please upgrade to a newer release. First of all, 10.0 is already out of support, which means that even if we found this to be a bug, it will not be fixed in your version. Then, we have made a large number of fixes, including some to build chains, which means that this might have already been fixed in newer releases. If it's not, we will need more information, such as the exact changes of the commits being built, and what changes are being "left out" of the builds, but we will only investigate it further if we can reproduce it in the newer releases.
I could not reproduce the problem on the latest version of TeamCity. But I can not say exactly what the last version of the problem is.
The problem is very unstable. The next day, I could not repeat the error, although before that I reproduced it 3 times. However, the servers did not reboot. Settings have not changed.
We are considering the possibility of switching to the latest version. But while I'm trying to solve the problem on this version.