![]() It also fixes a number of issues related to large Git repositories.īefore switching, make sure a native Git client version 2.29 or later is installed on your server machine, and the path to its executable is specified in the PATH environment variable. Switching to native Git improves the performance of the checking for changes operations on the server in comparison with the previously used JGit implementation. ![]() TeamCity can now use native Git as the default option for Git operations on the server. Native Git for VCS-related operations on the server Initial Git checkout may take significant time (sometimes hours), depending on the size of your project history, because the whole project history is downloaded during the initial checkout. Remote Run and Pre-Tested Commit are supported in the IntelliJ IDEA plugin with the Visual Studio Add-in, use the Branch Remote Run Trigger. If you get the related warning on running a build on some agent, we suggest that you update Git (the one specified in the TEAMCITY_GIT_VERSION parameter) and restart the agent. Git versions earlier than 2.10.0 will be deprecated in the future versions of TeamCity. The Git command-line client needs to be installed on the agents if the agent-side checkout is used. For common VCS root properties, see this section. This page contains description of the Git-specific fields of the VCS root settings. Git source control with Azure DevOps Services is supported (see authentication notes below). ![]()
0 Comments
Leave a Reply. |