search

renevanosnabrugge / vsts-promotepackage-task

Promote a package in VSTS to a Release View
MIT License
20 stars 25 forks source link

Providing multiple packages and versions for each #39

Open armanik11 opened 4 years ago

armanik11 commented 4 years ago

Currently I notice that Packages input can take a list of packages separated by a semi-colon or comma. But Version input can take only one value for all of those packages. Is that correct? If I have a need where I have 10 packages, each having different versions and I want to promote all, how can I do that?

Also I have considered creating my own task for other reasons for package promotion and I came across "Package Management" artifact source in Azure DevOps. Have you considered that as part of this task development? Just wanted to get your thoughts there.

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/artifacts?view=azure-devops (Search for Package Management)

NightOwl888 commented 4 years ago

If I have a need where I have 10 packages, each having different versions and I want to promote all, how can I do that?

You can use the package metadata feature to do that (screenshot). Alternatively, you could add 1 instance of the task per version, which is less flexible.

Also I have considered creating my own task for other reasons for package promotion and I came across "Package Management" artifact source in Azure DevOps. Have you considered that as part of this task development? Just wanted to get your thoughts there. https://docs.microsoft.com/en-us/azure/devops/pipelines/release/artifacts?view=azure-devops (Search for Package Management)

Could you explain exactly what you had in mind?

armanik11 commented 4 years ago

So Package Management artifact source let's users add a package and version as an artifact from a particular feed. Say I want to promote 10 package versions, I'll add 10 Package Management artifact sources. After that the custom task will get all the 10 packages and versions specified as artifact source and promote them.

armanik11 commented 4 years ago

Ping. Any thoughts? Also any plans to support universal packages? As there is no package metadata associated and the only way is to specify the package name and versions explicitly.

renevanosnabrugge commented 4 years ago

Hi! Thanks for your message. Supporting multiple versions is not something we will support for now. I propose multiple tasks or maybe use a task group to make it bit more concise. Universal packages should wor although the documentation still needs to be updated