|
Content with label agent in TeamCity 4.x Documentation (See content from all spaces)
Related Labels:
thread, manage, clean, extending, coverage, troubleshooting, license, server, enabled, directory, ant, disabled, authorized, environment, label, disconnected, plugin, disconnect, dump,
enterprise, property, trigger, key, system, professional, project, evaluation, home, committer, build, admin, process, remove, unauthorized, grid, setting, test, result, assign, status, edition, log, vcs, launchdaemons, requirement, search, connect, commercial, working, open, comment, configure, eap, properties, install, code, connected, deployment, ui, variable, upgrade, change, policy, compatible, hang, reference, predefined, configuration, run, backup, implicit
more »
Page:
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 ...
Other labels:
requirement, compatible, implicit, ui, admin
|
Page:
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 ...
Other labels:
ui, system, properties, environment, variable, clean
|
Page:
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 ...
Other labels:
build, home
|
Page:
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 ...
Other labels:
admin, requirement, implicit, compatible
|
Page:
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 ...
Other labels:
connect, disconnect, ui, remove
|
Page:
Agent-Side Extensions
page is obsolete and has been removed from the main TeamCity 4.x documentation space. Please refer to the Extending TeamCity section, and to the Agentside Object Model page in particular. Currently, there are two ways to extend a Build Agent: Write a custom build ...
Other labels:
plugin, extending, ant, deployment
|
Page:
Agent Startup Properties
page has been moved or marked as obsolete. Please refer to the TeamCity Startup Properties page. In TeamCity a build agent contains two processes: Agent Launcher Java process that launch the agent process itself Agent main process for a Build ...
Other labels:
system, property
|
Page:
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 ...
Other labels:
clean, working, directory
|
Page:
Assigning Build Configurations to Specific Build Agents
sometimes necessary to manage the Build Agents Build Agent' workload more effectively. 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 ...
Other labels:
build, configuration, project, run, policy, assign, requirement
|
Page:
Build Agent
TeamCity Build Agent is a piece of software that actually executes a build process. It is installed and configured separately from the TeamCity server. 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 ...
Other labels:
build, authorized, unauthorized, enabled, connected, disconnected, disabled, license
|
|
|