You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea here is that when we publish verticals, the publishing infrastructure should be generating a set of attributes for each artifact that indicates the AzDO Pipeline Artifact where the file could be found, as well as the subpath in that artifact. The arcade publishing infra then downloads from that location, rather than relying on static, known artifact locations.
The text was updated successfully, but these errors were encountered:
I've updated this branch to include the arcade changes and updated the bootstrap arcade with a build of this arcade that includes the changes.
I've updated eng/Publishing.props to specify the v4 publishing version.
I think that most of the existing infra structure should "just work". The specified Future* properties I think match what the VMR publishing does already.
Enable V4 publishing in VMR builds. Requires dotnet/arcade#15727.
The idea here is that when we publish verticals, the publishing infrastructure should be generating a set of attributes for each artifact that indicates the AzDO Pipeline Artifact where the file could be found, as well as the subpath in that artifact. The arcade publishing infra then downloads from that location, rather than relying on static, known artifact locations.
The text was updated successfully, but these errors were encountered: