TriggeredBy
Identifies the authority that triggered this build.
Properties
type
Returns the following values depending on the authority that triggered this build:
user if the build was triggered manually in TeamCity UI or via REST API.
snapshotDependency if the build is a part of a build chain and was requested by a downstream build configuration.
vcs if the build was initiated by the VCS Trigger that found new commits in the remote repository.
schedule if the build was initiated by the Schedule Trigger.
finishBuild if the build was initiated by the Finish Build Trigger.
retry if the build was initiated by the Retry Trigger that re-starts failed builds.
details
Optional details regarding the triggering event.
date
The timestamp of the build triggering.
displayText
The summary displayed next to the 'Triggered' line in TeamCity UI. Enumerates authorities that caused this build to run and displays the build's parent configuration name and number.
rawValue
The string representation of the properties
array.
user
Identifies the user who initiated a build, directly or indirectly. Indirectly means they initiated another build that eventuated the current one (for example, started a dependent build or triggered a build that failed and was then restarted by the Retry Trigger). Builds initiated by the Schedule Trigger do not have a related user.
build
A separate build that caused this one to run. Can co-exist with the user
field: for example, if a user triggered build A that requested (via a snapshot dependency) build B, the latter will have links to both the build A and the user who initiated it.
buildType
The parent build configuration of the build
.
properties
The array of name-value pairs containing service information about the triggered build and the events that initiated it.
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.