[wasm][xharness] install development SSL certificate on Helix agent before xharness run via SDK or powershell #53339
Conversation
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer |
|
/azp run runtime-libraries-mono outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
src/libraries/sendtohelixhelp.proj
Outdated
| --> | ||
| <PropertyGroup Condition="''$(TestPackages)' != 'true' and $(TargetsWindows)' != 'true' and '$(BrowserHost)' != 'windows'"> | ||
| <!-- install SDK so that, we could use `dotnet dev-certs https`. --> | ||
| <IncludeDotNetCli>true</IncludeDotNetCli> |
There was a problem hiding this comment.
Will IncludeDotNetCli be set for Windows as well?
There was a problem hiding this comment.
Maybe we can set this one in the bottom with HelixPreCommands?
There was a problem hiding this comment.
if powershell works for windows, we do not need full SDK.
There was a problem hiding this comment.
I know but we still need IncludeDotNetCli
There was a problem hiding this comment.
It's there by xharness already , but ok I will make it explicit https://github.com/dotnet/arcade/blob/6b9758661f4483a70654bcaf6f8d7c6a79ee5660/src/Microsoft.DotNet.Helix/Sdk/tools/xharness-runner/XHarnessRunner.targets
|
/azp run runtime-libraries-mono outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ghost
locked as resolved and limited conversation to collaborators
Caused by #53180, #53225
The original approach to install certificates didn't work because we don't have dotnet SDK, just runtime on some helix agents.
Fixes #53207