Where is the documentation for package resources?
It would appear the schema looks like this:
packages:
- package:
type:
connection:
name:
tag:
trigger:
version:
However, I'm unable to find any documentation on how these fields related to an ADO feed. I've been doing some trial and error and "universal" for type results in "No artifact type found corresponding to ID universal. Make sure that the artifact type extension is available and try again."
What should "connection" contain? I do not see a service connection type that appears appropriate, and I doubt the feed URL goes here (if so, how do you authenticate?)
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
could this be a duplicate of #7861 ?
It's a valid option (or appears to be, autocomplete works for the online editor). Entering something like "npm" for "type" doesn't throw an error when validating the yaml, either.
@kbuley Thanks for flagging this. We just pushed an update to the resources article that should be live shortly. The packages type only is for to GitHub packages now.
@kbuley Thanks for flagging this. We just pushed an update to the resources article that should be live shortly. The packages type only is for to GitHub packages now.
Is there WIP to include Universal packages? My use case is to allow for a specific rpm (since rpm is not supported by artifacts) to be selected at run time, defaulting to 'latest'. Much the same way that a build artifact is selectable at release creation time.
@kbuley I don't know offhand. Can you ask that question in our Developer Community?
@kbuley - I also want to know how to use Universal packages as a pipeline resource. Seems like a major oversight if it's not supported (also a major oversight if it's implemented and not documented).
I posted this request here:
https://developercommunity.visualstudio.com/idea/1154402/support-universal-packages-as-pipeline-resources.html
Most helpful comment
@kbuley - I also want to know how to use Universal packages as a pipeline resource. Seems like a major oversight if it's not supported (also a major oversight if it's implemented and not documented).
I posted this request here:
https://developercommunity.visualstudio.com/idea/1154402/support-universal-packages-as-pipeline-resources.html