-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Move to V3 publishing #6349
Move to V3 publishing #6349
Conversation
This is required for pushing packages up to the "VS 17.0" channel.
Looks like it works: https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=4667988&view=results |
The build did not kick off maestro promotion pipeline. I checked the darc get-build
The build is using the azdo internal repo url instead of the translated github url. Is there any reason why we cannot get the latest from .NET Eng - Latest channel? |
@epananth I think your concern would be solved by this PR: dotnet/arcade#7267 |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@MattGal is making a fix in arcade-validation to get this unblocked. I was able to test the changes he merged https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=4677589&view=results |
It will be good to run a test again.. |
Yaaay! finally :) |
Context
V3 publishing is much faster and is required for publishing to the "VS 17.0" channel.
Changes Made
Followed this: https://github.com/dotnet/arcade/blob/main/Documentation/CorePackages/Publishing.md#how-to-upgrade-from-v2-to-v3
Add eng\publishing.props with single propertygroup
PublishingVersion
set to 3.Pass
publishingInfraVersion: 3
to post-build yml.Testing
Should launch an exp/ branch to verify this
Added
exp/bevillal/v3-publish-test
as a default channel to "VS 17.0" and kicked off a pipeline build here: https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=4655204&view=resultsexp/bevillal/v3-publish-test
as a default channel from "VS 17.0"