BuildChanges
Retrieves the changes associated with the build.
Table Specific Information
Select
The provider uses the Azure DevOps API to process WHERE clause conditions built with the following columns and operators:
- ProjectId supports the '=' operator.
- BuildId supports the '=' operator.
- IncludeSourceChange supports the '=' operator.
NOTE: To improve performance, a single BuildId should be specified in the WHERE clause of the query.
For example:
SELECT * FROM BuildChanges WHERE ProjectId = '837ccd31-8159-4db3-b8ce-de0c36d2a0bf' AND BuildId = 3 SELECT * FROM BuildChanges WHERE ProjectId = '837ccd31-8159-4db3-b8ce-de0c36d2a0bf' AND BuildId = 3 AND IncludeSourceChange = true
Columns
Name | Type | References | Description |
Id [KEY] | String | Id of the build change. | |
ProjectId | String | Id of the project. | |
BuildId [KEY] | String |
Builds.Id | Id of the builds. |
AuthorDisplayName | String | This is the non-unique display name of the author. | |
AuthorId | String | Id of the author. | |
Location | String | The location of the full representation of the resource. | |
Message | String | The description of the change. | |
MessageTruncated | Boolean | Indicates whether the message was truncated. | |
Pusher | String | The person or process that pushed the change. | |
Timestamp | Datetime | The timestamp for the change. | |
Type | String | The type of change. 'commit', 'changeset', etc. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements, and offer a more granular control over the tuples that are returned from the data source. Unless otherwise specified, only the = operator is permitted when filtering on pseudocolumns.
Name | Type | Description | |
IncludeSourceChange | Boolean | Indicates whether to include source change. |