Label: agent

Content with label agent in TeamCity 4.x Documentation (See content from all spaces)
Related Labels: change , compatible , unauthorized , run , process , trigger , dump , admin , plugin , directory , disabled , build , open , grid , property , draft , manage , vcs , assign , environment , project , license , clean , authorized , hang , server , professional , implicit , test , evaluation , disconnect , home , configure , disconnected , backup , troubleshooting , connected , commercial , log , deployment , system , ant , label , connect , thread , status , reference , policy , setting , edition , global , code , properties , variable , install , enabled , requirement , enterprise , eap , remove , ui , configuration , predefined , working , search , comment , extending , upgrade , coverage , key , result , committer more »

7.Agent Requirements Administration > <build configuration> Agent requirements Use this page to specify the required Agent Requirements system properties and environment variables that build agents Build Agent must meet in order to be able to run the builds of the current build configuration. Option Description ...

Agent Details Agents > click agent name The contents of this page depend on whether the agent is connected or disconnected from the server. Connected Agent Option Description Agent summary Status This field shows date and time that the agent was connected and enabled/disabled to the TeamCity Server ...

Agent Home Directory Build Agent Home Directory is the directory where the agent has been installed. By default, the build agent files are installed in the following directory depending on the type of installer (distribution package) used: If the build agent was installed along with the server on the same machine ...

Agent Requirements Agent requirements are used in TeamCity to specify whether a build configuration Build Configuration can run on a particular build agent Build Agent. When a build agent registers on the TeamCity server, it provides information about its configuration, including its ...

Agents section: Item Description Install build agent Click this button to install an additional build agent, using one of the suggested techniques. Refer to Installing and Running Additional Build Agents Installation#installingBuildAgents for detailed instructions. Connected Agents An ...

Agent-Side Extensions Currently, there are two ways to extend a Build Agent: Write a custom build runner Write an extension to Ant Runner (for instance, to process custom tasks) In this section: Plugin Descriptor Spring container is used on the agent and server side. An example ...

Agent Startup Properties TeamCity a build agent contains two processes: Agent Launcher Java process that launch the agent process itself Agent main process for a Build Agent; runs as a child process for the agent launcher Whether you run a build agent via ...

Agent Working Directory Agent working directory is the directory on a build agent that is used as a containing directory for the checkout directories Build Checkout Directory. By default, this is the {{<Build agent home> Agent Home Directory/work}} directory. To modify the default directory location see Build Agent ...

Assigning Build Configurations to Specific Build Agents sometimes necessary to manage the Build Agents Build Agent' workload more effectively.&nbsp; For example, if the timeconsuming performance tests are run, the Build Agents with low hardware resources may slow down. As a result, more builds will enter the build queue ...

Build Agent build agent is a computer capable of running a build. Each build agent possesses a number of predefined parameters that make it compatible for creating certain builds. Build agents are joined into a build grid Build Grid. To create a build, TeamCity tries to select ...