Connect a release to a build in VSTS

For some reason there's no easy way to connect a release to a build when using REST API provided by

For some reason there's no easy way to connect a release to a build when using REST API provided by VSTS. Something which should be fairly trivial seems like a task, which is impossible to finish. However there's a "dirty" way of finding a build identifier, which is related to a release we're interested in.

Digging into release data

Let's consider following request:

/
https://{account}.vsrm.visualstudio.com/defaultcollection/{projectId}/_apis/release/releases/{releaseId}?api-version=3.0-preview.2

When called it'll returns a detailed information about a release including approvals, deployment steps, workflow and many more. When you dig deeper into a response, you'll find one section, which may help us here:

"artifacts": [{
	"sourceId": "{sourceId}",
	"type": "Build",
	"alias": "some_alias",
	"definitionReference": {
		"artifactSourceDefinitionUrl": {
			"id": "https://{account}.visualstudio.com/_permalink/_build/index?collectionId=",
			"name": ""
		},
		"definition": {
			"id": "{definitionId}",
			"name": "Name"
		},
		"project": {
			"id": "{projectId}",
			"name": "Name"
		},
		"version": {
			"id": "5854",
			"name": "2017.97"
		},
		"artifactSourceVersionUrl": {
			"id": "https://{account}.visualstudio.com/_permalink/_build/index?collectionId=&buildId=5854",
			"name": ""
		},
		"defaultVersionType": {
			"id": "selectDuringReleaseCreationType",
			"name": "Specify at the time of release creation"
		},
		"branch": {
			"id": "refs/heads/develop",
			"name": "refs/heads/develop"
		}
	},
	"isPrimary": true
}]

Of course I obscured it a little, but you should be able to get the picture. In the artifactSourceVersionUrl property you can see a URL, which itself isn't helping much. What we're interested in is the very end of it - it the query string it contains a buildId key, which directly points to the build used for this release. The only thing you have to do is to parse the JSON and extract identifier, which can be used further to query for a build.

Summary

Although REST API provided by VSTS is really helpful in most cases, this time I was really confused. Fortunately even indirect solutions are still solutions so as long as there's no other API version, this workaround seems valid uncomplicated.

Add comment