Move to V3 publishing#6349
Merged
benvillalobos merged 2 commits intodotnet:mainfrom Apr 22, 2021
Merged
Conversation
This is required for pushing packages up to the "VS 17.0" channel.
Member
Author
|
Looks like it works: https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=4667988&view=results |
Member
|
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? |
Member
Author
Member
Author
|
@epananth I think your concern would be solved by this PR: dotnet/arcade#7267 |
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
|
@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 |
Member
|
It will be good to run a test again.. |
epananth
approved these changes
Apr 22, 2021
Member
|
Yaaay! finally :) |
rainersigwald
approved these changes
Apr 22, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
PublishingVersionset to 3.Pass
publishingInfraVersion: 3to post-build yml.Testing
Should launch an exp/ branch to verify this
Added
exp/bevillal/v3-publish-testas 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-testas a default channel from "VS 17.0"