ApprovalInfo
If a build cannot start without a manual approval from specific reviewers, it stores related information in a related ApprovalInfo object.
Properties
compositeApprovals
The list of composite approval rules (combining multiple user or group requirements) that must be satisfied before this build can start.
status
The current approval status of this build. Possible values:
waitingForApproval — the build is queued and waiting for required reviewers to approve it.
approved — the build received the required number of approvals and is allowed to proceed.
timedOut — the build was automatically canceled because reviewers did not approve it within the allotted time.
canceled — a reviewer explicitly rejected and canceled the build.
canBeApprovedByCurrentUser
Returns true if the currently authorized user is among TeamCity users who can approve this build; otherwise, false.
userApprovals
The list of individual users whose approval is required to start a build.
groupApprovals
The list of user groups whose users need to approve a build before it can start.
timeoutTimestamp
The timestamp when the build is (or was) canceled due to reviewers failing to approve it on time. This value is calculated at the moment a build is queued.
configurationValid
Returns true if the configuration of users and user groups that should approve this build is valid; otherwise, false.
approvalReasons
Returns the reasons why TeamCity is waiting for build approval.
buildChainBuilds
The list of other builds (both upstream and downstream) that belong to the same build chain and require an approval.
Schema
Below, you can find a full schema of this object, in XML and JSON formats. You can choose what fields to submit depending on your current needs. Different methods might expect different fields: the best approach is to request this entity via GET and use the response as a base for the following POST request.
A link to another object implies that you can substitute it with the schema of the linked object, if it is required for your call.