Teamcity's revision incorrect.
We are relying on Teamcity’s revision calculation to determine the P4 last change list # and we are seeing weird behavior.
Below is a list of builds done. The build # we set is based on the date and the VCS change list reported by TeamCity (yymmdd_vcs.change.list). Notice that between the 2 builds there was no changes detected however the vcs.change.list number or revision has changed. Why is that?
Furthermore, if I look at the changelist/revision (28086349) that it is reporting using P4’s client, it’s in an area that is not included in our P4 workspace (all our code is in //Actuate/…)..
Please sign in to leave a comment.
Hi,
I'm afraid this is a question for perforce on how revision numbering is handled. TeamCity just picks up the revision number from the VCS Provider (in this case perforce), so we don't really have control over it. If you want those numbers to be somehow sequential even if that detaches them from the revision number, you can use the build counter that we provide for them, but usually the revision number is the one expected.
Regarding calculating changes, TeamCity tracks the repository as a whole and pulls the required information. It only displays changes related to the build configuration, but if the repository reports a new revision number with no changes, teamcity will update this information. This means that if you have a VCS Root for the whole repository, but your project only uses a part of it and is restricted properly to that part, only changes related to the appropriate project will be shown in yours, that's why you are seeing "no changes" and different revision number, because the changes do exist but in a part of the repository that doesn't relate to yours.
Hope this helps.