|
All content with label run.
Related Labels:
launch
, concepts
, delayed
, personal
, trigger
, system
, admin
, commit
, pre-tested
, custom
, build
, policy
, changes
, requirement
, property
, draft
, configuration
, ui
, assign
,
include
, environment
, project
, remote
, agent
, history
more »
4.Build Triggering
(TeamCity 4.x Documentation)
Administration > <project> > <build configuration> > Build triggering This configuration section allows you to specify events build triggers Build Trigger that will initiate builds of the particular build configuration. Option Description Pause/Activate Use this button to toggle the active and paused ...
|
Assigning Build Configurations to Specific Build Agents
(TeamCity 4.x Documentation)
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 ...
|
Assigning Build Configurations to Specific Build Agents
(TeamCity 3.x Documentation)
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 ...
|
Changes tab
(TeamCity 4.x Documentation)
Changes tab appears on the Build Results page and shows the list of changes included in build. The header of each entry contains the following information: !BuildChangesTab.png! By default, the headers are collapsed. Being expanded, each entry shows: VCS comment. Besides textual ...
|
Personal Build
(TeamCity 4.x Documentation)
personal build is a build initiated as Remote Run or PreTested Commit PreTested (Delayed) Commit. Only users with "Project Developer" role Role and Permission can initiate a personal build. The build uses the current VCS repository sources plus the changed ...
|
Personal Build
(TeamCity 3.x Documentation)
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 ...
|
Pre-Tested (Delayed) Commit
(TeamCity 4.x Documentation)
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 the changes to version control ...
|
Pre-Tested (Delayed) Commit
(TeamCity 3.x Documentation)
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 ...
|
Remote Run
(TeamCity 4.x Documentation)
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 of the state of the personal ...
|
Remote Run
(TeamCity 3.x Documentation)
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 ...
|
|
|
Label: run