[wasm][testing] create dev cert via powershell on helix #53225
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer |
premun
approved these changes
May 25, 2021
This was referenced May 26, 2021
radical
pushed a commit
that referenced
this pull request
May 28, 2021
…efore xharness run via SDK or powershell (#53280) Co-authored-by: Ankit Jain <radical@gmail.com> Caused by #53180, #53225 - The original approach to install certificates didn't work because we don't have dotnet SDK, just runtime on Helix agents. - dotnet dev-certs https needs user interaction with a dialog. Instead, using powershelgl to install certs - Wasm.Build.Tests are being disabled here because of #53405 Fixes #53207
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Caused by #53180
The original approach to install certificates didn't work because we don't have dotnet SDK, just runtime.
Fixes #53207