I use TC with git. The following features are used for VCS:
- branch specification `+:refs/heads/*`
- only checking out a part of the repository via checkout rules: `+:commons`
So the problem now is when e.g. the branch `device-modifiers-core` is builded (via VCS trigger). Instead of taking the head of the branch, it seems that a older commit is used. In TC i get the following:
[17:01:15][Compute revision for 'smec-services'] Upper limit revision: 4dcfd2cd64bb81f2d0e84ed6c7ff9c9458afe07b, maxModId 29765
[17:01:15][Compute revision for 'smec-services'] Latest commit attached to build configuration: 8b9862db1ef9d8a8f37b9bb9af0e92d47f05194b
[17:01:15][Compute revision for 'smec-services'] Computed revision: 8b9862db1ef9d8a8f37b9bb9af0e92d47f05194b
In this case, `4dcfd2cd64bb81f2d0e84ed6c7ff9c9458afe07b` is the correct head, but I have no idea why the commit `8b9862db1ef9d8a8f37b9bb9af0e92d47f05194b` is even showing up in here, because this is just the commit of a older tagged version of the master branch.
What does this `computed revision` means and why is it taken in favour of the head of the branch?