-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Sign the DAC and build (and sign) the cross-OS DACs in the VMR #46377
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I just noticed this is still in draft and I already reviewed. Sorry if some of my comments are on pieces that you plan to change/remove.
6bfcfb8
to
b515aa0
Compare
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from one comment.
Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.com>
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
The BuildPass2 job isn't building only the assets I want. I'll take a look tomorrow. |
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run sdk-unified-build-full |
Azure Pipelines successfully started running 1 pipeline(s). |
Depends on dotnet/runtime#111927 and code flow of dotnet/runtime#111416
Depends on #46532 (the code-flow of the changes into dotnet/sdk)
This will also require someone (likely @hoyosjs or @tommcdon) to authorize the
dotnet-unified-build
internal pipeline to use the AKV service connection before we make a release branch off of dotnet/dotnet.This change installs/uninstalls the DAC certificates around the build command on Windows and passes the correct arguments to the orchestrator to specify the path to the ESRP tool. It uses the templates defined by the runtime repo, which will be available in the VMR once dotnet/runtime#111416 has flowed all of the way to dotnet/dotnet.
It also adds a win-x86 join job for the cross-OS DAC builds. @ViktorHofer and I decided on using a separate join job as this is the only join point that depends on non-Windows non-ShortStack builds, so it may be the last job to start, and it may take near 20 minutes on its own (as we build all of the cross-OS DAC native code and do signing). By having it in its own job, we avoid slowing down the workloads + aspnetcore + sdk join job (which will only depend on Windows or ShortStack jobs)