This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
[release/3.0] Switch to Arcade yaml stage-based publishing with custom steps #7735
Conversation
This file contains 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
* Switch to stage-based publishing with custom steps * Workaround: allow known symbol publisher warnings Use Arcade-supported symbol publish workaround * Workaround: run gather drop dry to avoid flakiness * Use hosted pool for custom publish (cherry picked from commit 002bc9e) # Conflicts: # eng/Versions.props
dagood
added
the
* NO MERGE *
(cherry picked from commit 8a5f710)
dagood
removed
the
* NO MERGE *
Symbol publish is failing due to lack of space in the current agent pool. Move to a pool that is working for other jobs. This is temporary because Maestro++ will overwrite it with the next Arcade update.
|
Build and subscriptions went through in dotnet/extensions#2199 The next Arcade update (#7760) contains the expected fix for https://github.com/dotnet/core-eng/issues/7448, so there won't be a known build break when the temporary workaround is removed. Ready to merge to 3.0. @MichaelSimons PTAL |
MichaelSimons
approved these changes
Aug 19, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Ports #7725 to
release/3.0for #7118. For 3.0 serviceability.Ports #7754 to temporarily work around https://github.com/dotnet/core-eng/issues/7448.
Ports #7765, a fixup to how
-warnAsError:$falseis passed.One cherry-pick conflict: removing
<Channel>release/3.0</Channel>. This has been moved to a cross-branch mapping of BAR channels to dotnetcli channels inazure-pipelines.yml..NET Core 3 Devis mapped torelease/3.0.The new publish flow is not yet validated in
masterofficial builds./cc @wtgodbe @mmitche