|You are viewing documentation of TeamCity 5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.|
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 HTTP authentication.
To use a basic HTTP authentication instead of redirecting to the login page, prepend a path in usual TeamCity URL with "
The HTTP authentication can be useful when downloading build artifacts and triggering a build.
If you have Guest user enabled, it can be used to perform the action too. Use "
Triggering a Build From Script
To trigger a build, send the HTTP GET request for the URL:
Some tools (for example, Wget) support the following syntax for the basic HTTP authentication:
You can trigger a build on a specific agent passing additional
To trigger a build on two agents at the same time, use the following URL:
To trigger a build on all enabled and compatible agents, use "allEnabledCompatible" as agent ID:
Triggering a Custom Build
TeamCity allows you to trigger a build with customized parameters. You can select particular build agent to run the build, define additional properties and environment variables, and select the particular sources revision (by specifying the last change to include in the build) to run the build with. These customizations will affect only the single triggered build and will not affect other builds of the build configuration.
To trigger a build on a specific change inclusively, use the following URL:
To trigger build with custom parameters (system properties and environment variables), use the following syntax:
To specify a system property use a pair of parameters:
To specify an environment variable, use the following pair of parameters:
To move build to the top of the queue, add the following to the query string