![]() svn, CVS), and thus allows you to communicate with the repository from the build (for example, commit changes). The agent side checkout creates necessary administration directories (like. VCS client software has to be installed on the agent (applicable to Perforce, Mercurial, Git).Īgent checkout is usually more effective with regard to data transfers and VCS server communications. git) that is, the build script can perform VCS operations (for example, check-ins into the version control) - in this case ensure the build script uses credentials necessary for the check-in. Agent-side checkout frees more server resources and provides the ability to access version-control-specific directories (. The build agent will check out the sources before the build. Note that in the server checkout mode the administration directories (like. In some cases this checkout mode can lower the load produced on VCS repositories, especially if Clean Checkout is performed often, due to the caching of clean patches by the server. Thus, if you want to control who has access to the source repositories, the server side checkout is usually more effective. Network access to VCS repository can also be opened to the server only. Using this checkout mode, you need to install VCS client software on the server only (applicable to Perforce, Mercurial, TFS, VSS). The server side checkout simplifies administration overhead. Unless clean checkout is performed, the server sends to the agent incremental patches to update only the files changed since the last build on the agent in the given checkout directory. TeamCity optimizes communications with the VCS servers by caching the sources and retrieving from the VCS server only the necessary changes. Since the sources are exported rather than checked out, no administrative data is stored in the agent's file system and version control operations (like check-in, label or update) cannot be performed from the agent. The TeamCity server will export the sources and pass them to an agent before each build. Note that it will prevent commits to streams during the build. To disable the fallback in this case, you can enable the Create non-stream workspace option in the Perforce root settings. If a stream depot is used and the checkout rules are non-trivial (other than. If Perforce client cannot be found on the agent. ![]() The Git or Mercurial client is present on the agent, but is of the wrong version. No Git or Mercurial client is found on the agent. TeamCity falls back to the server-side checkout in the following cases: If the agent-side checkout is not possible, TeamCity will display a corresponding health report item and will use the server-side checkout (see the "Always checkout files on server" mode below). ![]() With this setting enabled, TeamCity will use the agent-side checkout (see the "Always checkout files on agent" mode below) if possible. When upgrading, the checkout mode settings for existing build configurations are preserved. This is the default setting for the newly created build configurations.
0 Comments
Leave a Reply. |