Clever Geek Handbook

GIT VCS doesn't update sources after Teamcity update

I recently upgraded to Teamcity 9 from 8. Since the upgrade, all my V2S GITs do not update sources. Build the log below, but the check directory is empty.

[04:33:49]Using vcs information from agent file: 53c2fd4d_Test.Project.xml
[04:33:49]Clean build enabled: removing old files from D:\Builds\Test.Project
[04:33:49]Checkout directory: D:\Builds\Test.Project
[04:33:49]Updating sources: server side checkout
[04:33:49][Updating sources] Will perform clean checkout. Reason: "Clean all files before build" turned on
[04:33:49][Updating sources] Transferring cached clean patch for VCS root: Test Project
[04:33:49][Updating sources] Repository sources transferred
[04:33:49][Updating sources] Removing D:\Builds\Test.Project

I tried clearing the server cache in <TeamCity Data Directory>/system/caches

but it didn't help.

+3


source to share


1 answer


We had the same problem. For a while, refs/heads/<BranchName>

<HASH>

we've seen tab changes for any body size will point back to fixation from time to time when upgraded from 8 to 9. Stubbornly ignoring any subsequent rebounds.

The reason for us may be the lack of licensed users in Stash. But in any TeamCity logs we looked, there was no sign of a git / stash / swabra error. This cache licensing issue was addressed by one part of our organization, while at the same time we:



  • check on

    Enable to use tags in the branch specification

    in the VcsRoot spec. (We don't actually use tags, and our branch spec templates will never match the tags in our stash / git repository.)
  • At this point, the web interface seems to be showing some totally crazy shifts. For build branch X, we saw commits from unlinked branches. However, the code you built was probably right. And every branch TeamCity has ever seen wanted to rebuild.
  • the TeamCity server bounced.
  • checked off

    , then on

    again, 'Allow tags in branch spec.

We then seem to be getting the correct changesets in the frontend. Of course, some of these steps are overkill. But this is what worked for us.

+1


source






More articles:


All Articles