|
Content with label run in TeamCity 3.x Documentation (See content from all spaces)
Related Labels:
agent, requirement, pre-tested, personal, project, concepts, policy, build, remote, configuration, delayed, assign, commit
Page:
Assigning Build Configurations to Specific Build Agents
Assigning Build Configurations to Specific Build Agents It is 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 ...
Other labels:
build, configuration, agent, project, policy, assign, requirement
|
Page:
Personal Build
Personal Build A personal build is a build initiated as Remote Run or PreTested Commit PreTested (Delayed) Commit. Only users with "Project Developer" role Role can initiate a personal build. The build uses the current VCS repository sources plus ...
Other labels:
concepts, personal, build, remote, delayed, commit
|
Page:
Pre-Tested (Delayed) Commit
PreTested (Delayed) Commit An approach which prevents committing defective code into a build, so the entire team's process is not affected. Submitted code changes first go through testing. If it passes all of the tests, TeamCity can automatically submit ...
Other labels:
delayed, pre-tested, commit, personal, build, remote
|
Page:
Remote Run
Remote Run A remote run is a Personal Build initiated by a developer from one of the supported IDE plugins to test how the changes will integrate into the project's code base. Unlike Pretested Commit Pretested (delayed) commit, no code is checked into the VCS regardless ...
Other labels:
remote, personal, build
|
Page:
Run Configuration Policy
Run Configuration Policy The run configuration policy allows you to select the specific build configurations you want a build agent to run. By default, build agents run all compatible build configurations and this isn't always desirable.  ...
Other labels:
configuration, policy
|
|
|