Skip to content

Conversation

weshaggard
Copy link
Member

@dseefeld this should fix the issue you are seeing with corefx not publishing packages.

Looks like when we tried to fix the corefx/coreclr package builds we based it off the wrong property.

dotnet/corefx#28607
dotnet/coreclr#17323

In those PR's we based it on DotNetBuildOffline but that is only set in the tarball not the source-build. We should instead update corefx and coreclr to use DotNetBuildFromSource for these conditions. I will submit a PR to change them.

Note that I'm only workaround the corefx in this PR because we don't actually use the identity packages from coreclr in our other builds.

@weshaggard
Copy link
Member Author

I've submitted PR's to fix the release/2.1 branches:
dotnet/coreclr#17846
dotnet/corefx#29418

@dagood
Copy link
Member

dagood commented May 1, 2018

@weshaggard @dseefeld Can you give some more detail about what this fixes? Where are the CoreFX identity packages used?

Edit: Nevermind, picked up what this is about from standup. Packages aren't being built in the online build, so we end up with all of CoreFX as prebuilt. The tarball build does create the packages, but it's uncertain whether they take over cleanly from the prebuilts (and we don't want the prebuilts in there regardless).

@weshaggard
Copy link
Member Author

@dotnet-bot test Debian8.4 Release
@dotnet-bot test RHEL7.2 Tarball Release

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.

4 participants