Skip to content

Few changes for corefx to follow arcade artifacts convention for packages - #3542

Merged
safern merged 2 commits into
dotnet:masterfrom
safern:UsePackageArtifactsConvention
Aug 7, 2019
Merged

Few changes for corefx to follow arcade artifacts convention for packages#3542
safern merged 2 commits into
dotnet:masterfrom
safern:UsePackageArtifactsConvention

Conversation

@safern

@safern safern commented Aug 1, 2019

Copy link
Copy Markdown
Member

No description provided.

@safern

safern commented Aug 2, 2019

Copy link
Copy Markdown
Member Author

Added NO MERGE label as we need to react in corefx and that change is not ready yet.

Comment thread src/Microsoft.DotNet.Build.Tasks.Packaging/src/build/Packaging.common.targets Outdated

@ericstj ericstj left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM modulo comment

@safern

safern commented Aug 2, 2019

Copy link
Copy Markdown
Member Author

/azp run arcade-ci

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@ViktorHofer ViktorHofer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you explain why you are using a different property now? ArtifactsPackagesDir

@safern

safern commented Aug 5, 2019

Copy link
Copy Markdown
Member Author

Can you explain why you are using a different property now? ArtifactsPackagesDir

Since we're moving towards following arcade's convention, PackageOutputPath will point to ArtifactsPackagesDir\{Shipping|NonShipping} depending on the pkproj's settings, if it has IsShipping=true or not. However, we want the specs and reports to be all together at the root dir for packages rather than having 1 specs/reports directory on each Shipping and NonShipping directory, ArtifactsPackagesDir is that root dir.

@ViktorHofer

Copy link
Copy Markdown
Member

OK 👌

@safern

safern commented Aug 7, 2019

Copy link
Copy Markdown
Member Author

Merging as I will be sending a PR to corefx shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants