|
Content with label run in TeamCity 4.x Documentation (See content from all spaces)
Related Labels:
property, trigger, agent, system, ui, requirement, changes, pre-tested, project, personal, concepts, policy, build, admin, remote, launch, environment, configuration, custom,
include, assign, delayed, history, commit
more »
Page:
4.Build Triggering
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. At the top of the page TeamCity displays the following information: current state Build ...
Other labels:
build, trigger, ui, admin, launch
|
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, agent, project, policy, assign, requirement
|
Page:
Changes tab
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 ...
Other labels:
changes, build, custom, trigger
|
Page:
Personal Build
personal build is a build initiated by the Remote Run procedure. 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 files identified during remote ...
Other labels:
concepts, personal, build, remote, delayed, commit, pre-tested
|
Page:
Pre-Tested (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 the changes to version control ...
Other labels:
delayed, pre-tested, commit, personal, build, remote
|
Page:
Remote Run
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 ...
Other labels:
remote, personal, build
|
Page:
Run Configuration Policy
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. The run configuration policy ...
Other labels:
configuration, policy
|
Page:
Run Custom Build Dialog
open the dialog: Click ellipsis on the Run button Click the Run build with these changes link on the Changes tab of the build results page build results home page To create history builds, TeamCity always uses the VCS roots and settings that are now ...
Other labels:
custom, build, property, environment, system, changes, include, history
|
|
|