I have created a release pipeline with the UI (classic, I guess) in Azure DevOps Services, that consumes build pipeline artifacts from several different build pipelines. I do not have a repo. In the release pipeline the artifacts are merged and then the final result is put in a zip file. This zip is the release.

The next step is to deploy the release to a team. Before I had the release pipeline, this deployment was done by sending an email with the zip attached. But now a release pipeline is needed, because the build pipeline artifacts are scattered across many build pipelines, to still keep this process automated.

The team that should get this deployment are not developers (do not have access to DevOps Services). It seems like deploying to a person using email is not possible. So, somehow I have to get hold of the physical zip file and put it where they can access it. Now I can only see in the logs that it was created. One idea I have is to put the zip in SharePoint, then I could start a Power Automate flow to send an email with a link to the zip. But I do not know if I can deploy to SharePoint from the release pipeline.

But surely there must be a simpler way to deploy a release to a person, with a release pipeline?

Please give me some good advice on how to proceed.

CodePudding user response：

There is a send email task that you can add at the end of your release pipeline. It can be downloaded from the Marketplace