[release/3.1] Update cert then rebrand #33034
Conversation
|
|
||
| [Fact] | ||
| [ConditionalFact] | ||
| [SkipOnHelix("https://github.com/dotnet/aspnetcore/issues/32813")] |
There was a problem hiding this comment.
There was a problem hiding this comment.
More proof that we weren't only running things on helix yet... SkipOnHelix has no effect on azdo jobs. The results file name is not the helix queue form either
There was a problem hiding this comment.
Skipping on linux since for some reason this test is failing only on ubuntu with the new cert
dougbu
left a comment
dougbu
left a comment
There was a problem hiding this comment.
WFM if you can get CI build working
|
Things are green now @dougbu not sure if I'm supposed to do anything else from here to get this in, but this should address the test failures in release/3.1 |
|
Nothing more to do 'til the release/3.1 branch is branded for 3.1.17. @dotnet/aspnet-build will get this in at the right time. |
|
(We may need to do branding in this PR to avoid CI failures in that work.) |
|
/fyi @Pilchie I marked this as |
|
FYI @dotnet/aspnet-build I'm doing branding in this PR |
dougbu
changed the title
|
/fyi I renamed the PR to cover what's going on |
Backport of #32812 to release/3.1
/cc @HaoK
Customer Impact
Testing
Risk