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

Migrate Internal OneBranch Automation to Undock Repo #4766

Open
4 of 15 tasks
nibanks opened this issue Jan 28, 2025 · 0 comments · Fixed by #4759
Open
4 of 15 tasks

Migrate Internal OneBranch Automation to Undock Repo #4766

nibanks opened this issue Jan 28, 2025 · 0 comments · Fixed by #4759
Assignees
Milestone

Comments

@nibanks
Copy link
Member

nibanks commented Jan 28, 2025

Describe the feature you'd like supported

To improve standardization and compliance of our internal build automation, we must migrate from mscodehub to the undock repo.

Proposed solution

P0

The first goal is to be able to generate VPacks for Windows.

  • Build kernel mode
  • Build user mode (schannel)
  • Remove generate-cmake.ps1 TODOs
  • Get user mode msquic.lib output
  • Fix test code header issue for trace stuff
  • Fix test code linking error
  • Build x86 user mode (not kernel), maybe arm too (let me check)
  • Get chpe working too

P1

The next goal is to migrate everything else.

  • Windows gamecore builds
  • Windows UWP builds
  • Windows openssl/openssl3 builds
  • Windows nuget packages (w/ publishing)
  • Linux openssl/openssl3 builds
  • Linux packages (w/ publishing)
  • Tests

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants