Azure-pipelines-tasks: Chain build/release

[cilerler]

is there a native way of trigger a build on another project when a release get completed?

I found that there is a marketplace item exist for this but wondering if this is available by Microsoft?

https://marketplace.visualstudio.com/items?itemName=benjhuser.tfs-extensions-build-tasks

[GitHubSriramB]

@cilerler - We do not have any native support for triggering build on a release completion.

The task that you pointed to in the extension is a good alternative. The other option would be to have your own PS script that can invoke the Build REST API to trigger build and include it within the appropriate environment in Release.

[cilerler]

In-case if anyone still looks for this feature https://blogs.msdn.microsoft.com/visualstudioalmrangers/2018/04/26/vsts-gems-chain-related-builds/

[e078108]

@GitHubSriramB is there any out of the box functionality from Microsoft to achieve this? Please do inform if there any references to PS script to get through this.

[cilerler]

@e078108 https://blogs.msdn.microsoft.com/visualstudioalmrangers/2018/04/26/vsts-gems-chain-related-builds/

[e078108]

@cilerler it doesn't help to trigger build from a release pipeline.

However this is how I solved it:

• Added an Agentless phase in release pipeline
• Used "Invoke REST API" task
• Used POST API to invoke the build (ref. to build definition ID)

[GarethOates]

Presumably the same thing can be done with releases? We have a number of different environments and lots of microservices each with their own build and release definitions. It would be nice to say "deploy all of these releases" to a particular environment (as defined in all definitions) and they would just all be released.

For example: Deploy releases [0,1,2,3...n] from branch master to environment DEV01.

[bansalaseem]

@GarethOates, you should able to deploy releases also via a custom task.