TeamCity On-Premises
 
Get TeamCity On-Premises
You are viewing the documentation for an earlier version of TeamCity On-Premises.

Changing Build Parameter Type and UI Appearance

Last modified: 26 April 2022

When adding a build parameter, you can extend its definition with meta-information, or specification. The parameter's specification defines how its controls are presented and validated in the Run Custom Build dialog.

By adding a typed specification to a parameter, you make it a typed parameter. Typed parameters are more understandable for non-developers and make experience with builds more user-friendly.

Example: A build configuration has a parameter that defines if a build has to include a license or not. The parameter can be either true or false (default). For a regular user, it might not be clear which build parameter is responsible for the license generation and what its values mean. It is not a problem when builds run with the default configuration. However, if a user wants to run a custom build, the variety of available parameters might confuse them. Using the build parameter specification, you can make the parameters' appearance in the Run Custom Build dialog more readable.

Typed parameter in a Running Custom Build dialog