Label: property

View: Popular Labels | All Labels

All content with label property.
Related Labels: runner , run , results , referencing , system , admin , msbuild , nunit , add , custom , build , jvm , global , changes , variable , draft , configuration , include , settings , more »

6.Properties and environment variables (TeamCity 4.x Documentation)
Administration > <project> > <build configuration> > Properties and environment variables <build configuration> > Edit configuration settings > Properties and environment variables Refer to the Properties of a Build Configuration section for properties description. System Properties Option Description \\ Predefined system properties \\ These readonly ...
Agent Startup Properties (TeamCity 4.x Documentation)
TeamCity a build agent contains two processes: Agent Launcher Java process that launch the agent process itself Agent main process for a Build Agent; runs as a child process for the agent launcher Whether you run a build agent via ...
Build Agent Configuration (TeamCity 4.x Documentation)
Configuration settings of the build agent are stored in a configuration file {{<TeamCity Agent Home>/conf/buildagent.properties}}. The file can also store properties that will be published on the server as Agent properties and can participate in the agent requirements expressions. Also, all the system and environment ...
Build Parameters tab (TeamCity 4.x Documentation)
Build Parameters tab appears on the Build Results page and shows the list of system properties and environmental variables which were used by a particular build. The properties and variables set depends on the settings of the build configuration. The following picture shows an example ...
Defining Properties (TeamCity 4.x Documentation)
system properties and environment variables required for a build configuration can be defined in three locations. Where these properties and variables are set will determine whether they affect a specific build configuration, all of a project's build configurations that use the same VCS root, or a specific ...
MSBuild_ (TeamCity 4.x Documentation)
NET Testing Frameworks Support NUnit Support \\ See Also: Concepts: build runner Administrator Reference: NUnit for MSBuild
Predefined Properties (TeamCity 4.x Documentation)
section contains description for: Global Properties Global properties can be used for setting various build configuration settings (use "{{%system.<propertyname>%}}" syntax) and inside build scripts (use property names as they are). Property Name Value teamcity.build.checkoutDir Working folder ...
Referencing Properties (TeamCity 4.x Documentation)
build configuration administration screens the properties can be referenced by {{%system.<property name>%}} and {{%env.<property name>%}}. Only the properties defined on agent and in the build configuration itself can be referenced. Any userdefined property can reference other properties by using ...
Run Custom Build Dialog (TeamCity 4.x Documentation)
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 ...
Server Startup Properties (TeamCity 4.x Documentation)
you run the server using the {{runAll}} or {{teamcityserver}} scripts, you can set the options via {{TEAMCITYSERVEROPTS}} environment variable. If you run the server as Windows service, run Tomcat's service configuration editor by executing the command tomcat6w.exe //ES//TeamCity ...