![]() The TeamCity server only distributes builds to agents that are enabled.Īgent disabling does not affect (stop) the build which is currently running on the agent.ĭisabled agents can still run builds when the build is assigned to a special agent (for example, by triggering a custom build). If a build agent is installed and running on the same computer as the TeamCity build server, it is authorized automatically.Įnabled/ Disabled (Disabled for maintenance for cloud agents)Īgents are manually enabled/disabled via the web UI. When a new agent is registered on the server for the first time, it is unauthorized by default and requires manual authorization to run the builds. Purchase additional licenses to expand the number of agents that can concurrently run builds. When an agent is unauthorized, a license is freed and a different build agent can be authorized. The number of authorized agents at any given time cannot exceed the number of agent licenses entered on the server. Only authorized build agents can run builds. ![]() The default timeout duration (14 days) can be adjusted by changing the .inactivityDays internal property.Īgents are manually authorized via the web UI on the Agents page (except for the agents from the machines launched by the cloud integrations). If you try to reconnect it to the server, you will have to authorize it again. If an agent stays disconnected during 14 days, its state changes to Unauthorized. In TeamCity, a build agent can have following statuses:Īn agent is connected if it is registered on the TeamCity server and responds to server commands, otherwise it is disconnected. The TeamCity server monitors all the connected agents and assigns queued builds to the agents based on compatibility requirements, agent pools, build configuration restrictions configured for an agent and the selection algorithm described here. An agent can run builds of any compatible build configuration. The number of agents basically limits the number of parallel builds and environments in which your build processes are run. An agent can run a single build at a time. An agent can be installed on the same computer as the server or on a different machine (the latter is a preferred setup for server performance reasons) an agent can run the same operating system (OS) as the TeamCity server or a different OS.Ī TeamCity build agent contains two processes:Īgent launcher - a Java process that launches the agent process.Īgent - the main process for a build agent runs as a child process for the agent launcher.Īn agent typically checks out the source code, downloads artifacts of other builds and runs the build process. It is installed and configured separately from the TeamCity server. 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 |