This repository was archived by the owner on Jan 23, 2023. It is now read-only.
[release/3.0] Move corefx to stages, use arcade's package artifacts convention - #40198
Merged
Conversation
…net#40124) * Move corefx to stages, use package artifacts convention start transition to use arcade publish tasks * Update arcade dependencies from build 20190808.13
ViktorHofer
approved these changes
Aug 9, 2019
Member
Author
|
Merging as this is required for next release. |
safern
added a commit
that referenced
this pull request
Aug 9, 2019
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Port #40126 to 3.0
Description
Changes our build templates to use azure devops stages and include Arcade publish system with signing and nuget validation. Also, changes the directory structure on how we bin place packages in the artifacts dir to follow arcade's convention based on
ShippingandNonShipping.Customer Impact
None.
Regression?
No.
Risk
Low.
Easier to review by hiding white spaces.
cc: @danmosemsft