No Changes are displayed for the first build ever
I setup new ssh git vcs root to our on-premises Bitbucket server, setup new configuration, and I don't see any changes.
Is this only me?
With such limitation I cannot start build from the commit pushed to git before I created this TeamCity configuration.
I think it lacks a feature to show last 1000 commits for new configurations for each vcs.
Another problem this creates is related to the fact that Teamcity sometimes stops showing changes for configuration (while still building with correct git hash of the last commit on the branch!!!). The changes are stuck at some commit from a totally unrelated branch. I suspect this happens after our engineers play with branch specifications and default branch switching from short to full (with refs/heads). The only way to fix TeamCity configuration in this condition it is to copy it into a new name. But again: no changes anymore.
Please sign in to leave a comment.
Hi Vyacheslav. It's not you: currently, there is a limitation that doesn't allow us running the builds on the changes created before the build configuration. Here is a related feature request: https://youtrack.jetbrains.com/issue/TW-10211. Please vote/watch.
Regarding the branch specification change, VCS changes are displayed per branch logical name. If after the branch specification change the logical branch name is no longer in the specification, the change will not be displayed in the logical branch name. However, you will be able to see the changes if you select the new logical branch name via branch selector dropdown.
E.g. if the branch specification is '+:refs/heads/(develop)', the logical branch name will be 'develop'. If the branch specification is changed to '+:refs/heads/develop', the logical branch name will be 'refs/heads/develop'. The changes you commit to the corresponding branch will not be shown in 'develop', but you will see them in 'refs/heads/develop'.