"Changes are collected, there are no changes found."
We are seeing several builds in the build queue triggered by Git:
"Changes are collected, there are no changes found."
I haven't been able to find any published information on what this means. Can you help?
Please sign in to leave a comment.
Hi Rob,
The message just means that TeamCity has communicated with the VCS repository and got (current) revisions to be used in the build. Since previous build (or last VCS settings changing time) there were no new commits found in the repository.
If there are changes in the repository, it makes sense to double-check the VCS root and checkout rules settings and post here the details of the settings with the details of the repository changes which you think should be shown in TeamCity.
I am curious why we are seeing this message as I would expect the VCS trigger only to fire when there *are* changes in the repo.
Rob,
There are different cases when this might happen.
You can check the "triggered by" of the build to double-check how this specific build was triggered. "Triggered by" of the previous build might be also worth checking as it might be the build was triggered manually and by the trigger around the same moment.
If you feel there is a bug in TeamCity, it makes sense to ensure you are running TeamCity 2017.1.x and report all the details in our tracker or support channel.