TeamCity 7.1 only checks out latest revision of branch if trunk's latest revision > branch's revision
Hello,
We are using TeamCity 7.1, build 23907.
When we try to build from branch, TeamCity will check out only the revision that is lower than the latest revision in trunk.
For example, if trunk has r100, r101 and r103, and branch has r99 and r104, TeamCity will check out r99. If we then commit something to trunk, and thus bump it to r105, TeamCity will happily comply and check out r104 when we try to build the branch.
I suspect it has to do with the way TeamCity is configured for us, but am unclear as to what we'd have to change. (I just very recently joined a new team, and this is the first time I'm trying to use TeamCity...)
On the "start page", when we click the ellipse "..." button next to the "Run" button of a project to open the "Run Custom Build xyz :: abc" window, on the "Changes" tab, it only shows revisions for trunk.
On the Build Parameters tab in the same window, we have two boxes that might have to do with the issue:
- Checkout Rule (Trunk/branch)*: "trunk" or "branches/OurProject-"
- Checkout Branch version*: text box, for branches we enter sth. like "4.12". We leave it empty when we selected trunk above.
The checkout rules are puzzled together from these two boxes, so we'd get e.g. "branches/OurProject-4.12".
The SVN URL for the VCS root is basically http://svn.example.com/svn/ourproject/, and we have the normal SVN folder structure (tags, trunk, branches) below that...
Any idea what we need to do (config-wise) to get this issue sorted, and to always check out HEAD when we try to get a branch - regardless of when we last committed to trunk?
Kind regards,
Christian
Please sign in to leave a comment.
Hi Christian,
Our first comment would be to mention that you are using a really outdated version of TeamCity, and that you should upgrade. Then, a number of issues from subversion not loading the correct revisions under some circumstances were fixed around version 8.1, so again an upgrade would likely help fix the problem.
Additionally, the build logs for the builds that don't pick up the correct revision usually include a line with the calculated revision for the build (in case it's a part of a dependency chain and the revision must be different under some conditions). In the latest releases we introduced a change where this log calculation line also adds an explanation on why the revision isn't the latest, in case it isn't, so even if the specific issue hadn't been fixed, you would have extra information to try and figure out the problem.
Without updating, in the build log you might be able to see which revision it's picking, which branch, also you might check the parameters tab on a build result and see whether the parameters were being applied correctly. Beyond that, there is very little we can suggest right now for such an old version, I'm afraid.