|
All content with label properties.
Related Labels:
admin, clean, synchronization, configuration, environment, agent, variable, ui, system, ldap, server, build
Page:
Agent Details
(TeamCity 6.0.x Documentation)
Agents > click agent name The contents of this page depend on whether the agent is connected or disconnected from the server. Connected Agent Option Description Agent summary Status This field shows date and time that the agent was connected and enabled/disabled to the TeamCity Server ...
Other labels:
ui, agent, system, environment, variable, clean
|
Page:
Agent Details
(TeamCity 5.x Documentation)
Agents > click agent name The contents of this page depend on whether the agent is connected or disconnected from the server. Connected Agent Option Description Agent summary Status This field shows date and time that the agent was connected and enabled/disabled to the TeamCity Server ...
Other labels:
ui, agent, system, environment, variable, clean
|
Page:
Agent Details
(TeamCity 4.x Documentation)
Agents > click agent name The contents of this page depend on whether the agent is connected or disconnected from the server. Connected Agent Option Description Agent summary Status This field shows date and time that the agent was connected and enabled/disabled to the TeamCity Server ...
Other labels:
ui, agent, system, environment, variable, clean
|
Page:
Agent Details
(TeamCity 3.x Documentation)
Agent Details Agents > click agent name The contents of this page depend on whether the agent is connected or disconnected from the server. Connected agent Option Description \\ Agent summary \\ Status This field shows date and time that the agent was connected and enabled ...
Other labels:
ui, agent, system, environment, variable, clean
|
Page:
Properties of a Build Configuration
(TeamCity 4.x Documentation)
Properties of a Build Configuration provide you with a flexible means of sharing settings within a single Build Configuration, managing compatible agents based on specific environment (see Agent Requirements 7.Agent Requirements) and a convenient way of passing generic or environmentspecific settings ...
Other labels:
build, configuration, system
|
Page:
Properties of a Build Configuration
(TeamCity 5.x Documentation)
Properties of a Build Configuration provide you with a flexible means of sharing settings within a single Build Configuration, managing compatible agents based on specific environment (see Agent Requirements 7.Agent Requirements) and a convenient way of passing generic or environmentspecific settings ...
Other labels:
build, configuration, system
|
Page:
System Properties for Running the Server
(TeamCity 3.x Documentation)
System Properties for Running the Server Various aspects of TeamCity's behavior can be customized through a set of JVM options. The options can be specified using the {{\D}} parameter passed to the JVM running the TeamCity server or agent. e.g. Dteamcitylogs=../logs/ If you ...
Other labels:
admin, server, agent
|
Page:
System Properties of a Build Configuration
(TeamCity 3.x Documentation)
System Properties of a Build Configuration Various build configuration settings can be defined by referencing Build Configuration Properties. Build Configuration Properties are either userdefined or predefined. In this section: Defining properties #def Referencing properties #ref Predefined properties #pre ...
Other labels:
build, configuration, system
|
Page:
Typical LDAP Configurations
(TeamCity 7.x Documentation)
page contains samples of {{ldapconfig.properties}} file for different configuration cases. Basic LDAP Login Backup LDAP server is specified. Provided users can log in into LDAP with "{{EXAMPLE\Username}}", they log in into TeamCity also as "{{EXAMPLE\Username}}", username stored in TeamCity ...
Other labels:
ldap, synchronization
|
Page:
Typical LDAP Configurations
(TeamCity 6.5.x Documentation)
page contains samples of {{ldapconfig.properties}} file for different configuration cases. Basic LDAP Login Backup LDAP server is specified. Provided users can log in into LDAP with "{{EXAMPLE\Username}}", they log in into TeamCity also as "{{EXAMPLE\Username}}", username stored in TeamCity ...
Other labels:
ldap, synchronization
|
|
|
Label: properties