How should I publish my distributable release files in a release pipeline?

Copper Contributor

Hello community, I have been looking up quite some time on the subject of pipelines, but strangely, I cannot get to find an answer for this very simple scenario I have.


Thing is, the releases to our software need to be published as a easily downloadable and versioned file/s or installer. Why? Because due to the nature of the bussiness, target environments do not have internet connection, so we need to offer manually downloadable distributable files/installer to manually install them.


I have tried different things but these don't seem to work for me:


- Publish as a "Pipeline Artifact": This option doesn't work in classic Release Pipelines (it throws an error "Cannot upload to a pipeline artifact from release environment.").


- Publish as a "Build artifact": If I do it in a build pipeline, it will defeat the purpose of separation between "build" and "release" pipelines. Even if I did it anyway, it will be published as a "build" artifact, which will be very hard to reach in the Azure Devops web app: Pipelines>(Pipeline name)>(browse run name)>Artifacts>Artifact name, which also gets deleted like 30 days after.


- Publish with "Universal Publish": This option seems to be very apt, since releases are added into the Azure Artifacts feed with a corresponding version number in a very "official" manner (i yet have to see how to assign this version number dynamically from build stage). But the problem is that apparently it's not possible to download universal packages from Azures Web App UI for technical reasons. Instead, I have to use Azure CLI. But i need to be able for me or any team member to download this artifact easily and without installing additional software or technical knowledge.


Am I missing something here?


Some considerations: we only have an Azure Devops plan, no other Azure services (storage, etc).




0 Replies