Solution: Team City build fails to pickup latest Git commit and results in "The upper limit revision does not have information about corresponding branch, the first branch revision is unknown"

Ok, we finally ran into this same issue. We recently upgraded our Team City environment and numerous TC builds started to break since TC wasn't able to pickup the Git commits on our feature branches. Everything worked fine before the upgrade but was broken afterwards. And not all of our TC builds were broken. So my team and I went through the broken builds and found that the TC builds trigger was slightly different than the TC builds that continued to work.

Each TC build had a VCS trigger that had a Quiet period mode set to the default value of 60 or some other custom value. Once we deleted the VCS trigger and recreated it with the default values, TC started to see our Git commits and used them in the build that was kicked off.

Just a suggestion for those of you that run into this issue.

Original VCS trigger value

New VCS trigger after we deleted the original one and recreated it with the defaults: