Content-Length: 233374 | pFad | http://github.com/dotnet/dotnet/issues/708

80 Enable V4 publishing in VMR builds · Issue #708 · dotnet/dotnet · GitHub
Skip to content

Enable V4 publishing in VMR builds #708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mmitche opened this issue May 13, 2025 · 1 comment
Open

Enable V4 publishing in VMR builds #708

mmitche opened this issue May 13, 2025 · 1 comment
Assignees

Comments

@mmitche
Copy link
Member

mmitche commented May 13, 2025

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.

@mmitche
Copy link
Member Author

mmitche commented May 13, 2025

@mmitche mmitche moved this to In Progress in .NET Unified Build May 14, 2025
@ViktorHofer ViktorHofer transferred this issue from dotnet/source-build May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/dotnet/dotnet/issues/708

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy