Represents TeamCity build template.
To appear in UI a template should be registered in a project using the template method.
The id and name are mandatory properties for a valid template (id can be omitted if it matches the class name).
Template settings are grouped into blocks similar to tabs in the build template admin UI:
options available on the General Settings tab are defined as properties
Creates an instance of this template via reflection using a no argument constructor, used during copying. Throws an error if this class doesn't have a default constructor. Subclasses can override it to create an instance without using a default constructor.
BuildType or template id. It appears in the web UI and is used in urls. If the entity has a uuid specified, then the id can be changed at any time. If uuid is omitted, then TeamCity treats an entity with a changed id as a new entity, all data associated with the old entity will be lost (e.g. a build history). Id can also be used by some settings, e.g. as a part of parameter reference. If you change the id, you should find all its occurrences in the current project and change them too. Id must be unique across all buildTypes and templates on the server. If id is missing, it will be generated from the class name (if the class is not from the
Allows to set maximum number of simultaneously running builds per branch. Each line must be in form of branch:number, where branch is either a logical branch name or a pattern containing and number specifies the maximum number of builds which can be simultaneously running in each branch matching the pattern. 0 means there is no limit.