Skip to content
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

Support Windows builds in release/2.1 up to Core-Setup #898

Closed
dagood opened this issue Nov 16, 2018 · 1 comment
Closed

Support Windows builds in release/2.1 up to Core-Setup #898

dagood opened this issue Nov 16, 2018 · 1 comment
Assignees

Comments

@dagood
Copy link
Member

dagood commented Nov 16, 2018

This issue is to support Windows builds up to Core-Setup (Microsoft.NETCore.App), add it to AzDO CI, and flow the work through to release/2.2 and master. We have non-Windows-only change debt, and want to get ahead of it before the more dramatic build flow changes coming soon.

master currently has a Windows build, but it is a special case causing difficulties when auto-merging and upgrading.

A few things that can be built on top of this, but aren't included:

  • Build the SDK. We know we have some issues to work through in the submodules before we can do this.
  • Add Windows smoke-test to CI #904 Smoke-test support. (Requires a full SDK/CLI build, right now. Maybe we could work around it to use the tooling SDK with source-built Runtime.)
  • Building a tarball that can build (offline) on Windows. This doesn't address any known real-world scenario. The only thing I can think of is it would potentially be a convenience for Microsoft devs to work with the offline build flow while on Windows, if they aren't used to Linux.
@dagood
Copy link
Member Author

dagood commented Nov 20, 2018

Closing, merged into 2.1. New issues: #904 (smoke-test) #907 (prebuilt baseline)

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

No branches or pull requests

1 participant