Label: build

View: Popular Labels | All Labels

Content with label build in TeamCity 4.x Documentation (See content from all spaces)
Related Labels: clean, coverage, utility, maven2, pause, dependent, server, enabled, copy, directory, navigation, label, rule, commit, reordering, root, trigger, graph, compare, more »

Page: .NET Testing Frameworks Support
support the realtime reporting of test results, TeamCity should either run the tests using its own test runner or be able to interact with the testing frameworks so it receives notifications on test events. Custom TeamCityaware test runners are used to implement ...
Other labels: nunit, launcher, utility, runner, windows, gallio, xunit
Page: 1.General Settings
Administration > <project> > <build configuration> > General Settings Item Description \\ Name Edit the name of the build configuration. The build configuration name should not contain special characters. \\ Description Enter an optional description. \\ Build number format Specify the build ...
Other labels: configuration, settings, ui, general
Page: 2.Version Control Settings
Administration > <project> > <build configuration> > Version Control Settings Administration > Configure VCS roots > <vcs root> > Version Control Settings This page describes the options available on the Version Control Settings page when editing build configurations: VCS Roots ...
Other labels: vcs, root, configuration, label, labeling
Page: 3.Build Runners
Administration > <project> > Runner <build runner> This section provides descriptions of the following build runners Build Runner supported by TeamCity: Ant Maven2 NAnt MSBuild sln2003 Microsoft Visual Studio 2003 solutions sln2005 Microsoft Visual Studio 2005 ...
Other labels: ui, runner, admin
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: trigger, ui, admin, run, launch
Page: Accessing Server by HTTP
Accessing Server from Scripts The TeamCity server supports basic HTTP authentication allowing to access certain web server pages and perform actions from various scripts. Use valid TeamCity server username and password to authenticate using basic ...
Other labels: admin, server, script, trigger
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: agent, home
Page: Ant
page contains reference information about the Ant build runner fields: Option Description \\ Build runner \\ Select Ant from the dropdown list. \\ Ant Parameters Option Description Path to build.xml file If you choose the option, you can ...
Other labels: ant, runner
Page: 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 ...
Other labels: configuration, agent, 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: agent, authorized, unauthorized, enabled, connected, disconnected, disabled, license