Skip to content

Do not always build the targeting pack archives #16781

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

Merged

Conversation

mmitche
Copy link
Member

@mmitche mmitche commented Nov 3, 2019

No description provided.

@mmitche mmitche requested a review from a team as a code owner November 3, 2019 00:29
@wtgodbe
Copy link
Member

wtgodbe commented Nov 3, 2019

Would be interested to know why this didn't surface before servicing builds, but that's a question for later

@wtgodbe
Copy link
Member

wtgodbe commented Nov 3, 2019

CC @JunTaoLuo @dougbu

@dougbu
Copy link
Contributor

dougbu commented Nov 3, 2019

This may work but is likely glossing over a deeper problem.


$(OnlyPackPlatformSpecificPackages) is no longer honoured for the .Ref package. The main problem is at https://github.com/aspnet/AspNetCore/blob/release/3.0/src/Framework/ref/Microsoft.AspNetCore.App.Ref.csproj#L211

Where before $(OnlyPackPlatformSpecificPackages) ensured $(IsPackable) was false for the generic .Ref project and therefore the package wasn't built, the new $(IsTargetingPackPatching) property takes precedence.

@JunTaoLuo @wtgodbe why do both $(IsTargetingPackPatching) and $(IsTargetingPackBuilding) exist? And, if they're both necessary, why aren't both used to set $(IsPackable) earlier in the .Ref project (here)?


@mmitche I recommend changing https://github.com/aspnet/AspNetCore/blob/release/3.0/src/Framework/ref/Microsoft.AspNetCore.App.Ref.csproj#L7-L8 (to include $(IsTargetingPackPatching) in the condition) instead of anything in Publishing .props. Also back out the use of $(IsTargetingPackPatching) at https://github.com/aspnet/AspNetCore/blob/release/3.0/src/Framework/ref/Microsoft.AspNetCore.App.Ref.csproj#L211

We can remove $(IsTargetingPackPatching) later…

@wtgodbe
Copy link
Member

wtgodbe commented Nov 3, 2019

IsTargetingPackPatching really means "Is this 3.0.1?". we use it for some special logic in ResolveReferences.targets

@mmitche
Copy link
Member Author

mmitche commented Nov 3, 2019

@wtgodbe @JunTaoLuo @dougbu I'll leave it to you to decide whether this is okay to take or whether another fix is needed. Merge as desired.

@wtgodbe
Copy link
Member

wtgodbe commented Nov 4, 2019

@dougbu I'm confused by your suggestion - IsTargetingPackPatching is just based off of whether or not we're building 3.0.1. Adding it as a condition to https://github.com/aspnet/AspNetCore/blob/release/3.0/src/Framework/ref/Microsoft.AspNetCore.App.Ref.csproj#L7-L8 wouldn't change the behavior

@wtgodbe
Copy link
Member

wtgodbe commented Nov 4, 2019

@dougbu
Copy link
Contributor

dougbu commented Nov 4, 2019

Does that sound correct?

Yup, glad I wasn't delusional. Let me know if you want me to create another PR for that one-liner. Not sure reusing this PR makes sense.

@mmitche mmitche force-pushed the remove-targeting-pack-from-most-publish branch from b19dc69 to 5bcbb16 Compare November 4, 2019 03:27
@mmitche
Copy link
Member Author

mmitche commented Nov 4, 2019

I've changed this PR to use will's suggestion and run an internal build to test.

@mmitche mmitche changed the title Remove the targeting pack archives from publish except for windows x64 Do not always build the targeting pack archives Nov 4, 2019
@dougbu
Copy link
Contributor

dougbu commented Nov 4, 2019

thanx @mmitche❕❕

Copy link
Contributor

@JunTaoLuo JunTaoLuo left a comment

Choose a reason for hiding this comment

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

Rerunning flaky test.

@mmitche mmitche merged commit 0b713e5 into dotnet:release/3.0 Nov 4, 2019
@mmitche mmitche deleted the remove-targeting-pack-from-most-publish branch November 4, 2019 14:45
@analogrelay analogrelay added this to the 3.0.1 milestone Nov 14, 2019
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.

5 participants