Note that the data travelling through the connection established from an agent to the server includes build settings, repository access credentials and keys, repository sources, build artifacts, build progress messages, and build log. If the agents and the server are deployed in a secure environment, agents can be configured to use plain HTTP URL for connections to the server as this reduces transfer overhead. It is recommended using HTTPS for agent-to-server communications (check related server configuration notes). This is called unidirectional agent-to-server connection.Īgents use unidirectional agent-to-server connection via the polling protocol: an agent establishes an HTTP(S) connection to the TeamCity Server, and polls the server periodically for server commands. Moreover, the build procedure can slow down the responsiveness of the web UI and overall TeamCity server functioning.Ī TeamCity agent connects to the TeamCity server via the URL configured as the serverUrl agent property. This is not a recommended setup for production purposes because of security concerns. If you install TeamCity bundled with a Tomcat servlet container, or use the TeamCity installer for Windows, both the server and one build agent are installed on the same machine. Before that, make sure to read notes on agent-server communication, system requirements, conflicting software, and security. A production TeamCity setup requires installing additional build agents on dedicated machines. A TeamCity build agent is a piece of software which listens for the commands from the TeamCity server and starts the actual build processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |