-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Try using helix sdk support directly again #23585
Conversation
@Tratcher @jkotalik looks like all of the IIS functional tests are failing on this PR, but everything else is working, can you guys take a look and see if its obvious what's going on? The main difference in this PR is we switched to using the build in helix sdk support, so its possible some of the paths and side effects are slightly different, not sure if IIS functionals are relying on anything there... |
Direct link to a build with the failing tests, since I'm going to fix a build warning in the PR: |
Status of this PR is waiting for the arcade changes to propogate, and then rebase to see if things go green (NetCoreSDK isn't set right now so runs are all broken) |
What arcade changes is this waiting on? Is this blocked on #23978? |
Yes |
FYI this should be unblocked. |
Nice, with the new arcade changes, looks like the built in helix sdk support works for us now, marking as ready for review |
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.
Change looks fine. Just not positive whether it improves one area.
set DOTNET_HOME=%HELIX_CORRELATION_PAYLOAD%\sdk | ||
set DOTNET_ROOT=%DOTNET_HOME%\%$arch% | ||
set DOTNET_ROOT=%HELIX_CORRELATION_PAYLOAD%\dotnet | ||
set DOTNET_HOME=%DOTNET_ROOT% |
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.
In our previous conversations about this change and about incorrectly changing the payload folders, I got the impression we were getting out from under the payload folders with this PR. Won't we hit leftover files still❔
I'm hoping this is fine and that I misunderstood you and @MattGal 😈
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.
If we want to install the runtime to a different directory we can still do that in a different PR, that's orthogonal to using the sdk support
@@ -117,8 +117,8 @@ Usage: dotnet msbuild /t:Helix src/MyTestProject.csproj | |||
<TestAssembly>$(TargetFileName)</TestAssembly> | |||
<PreCommands>@(HelixPreCommand)</PreCommands> | |||
<PostCommands>@(HelixPostCommand)</PostCommands> | |||
<Command Condition="$(IsWindowsHelixQueue)">call runtests.cmd $(TargetFileName) $(NETCoreSdkVersion) $(MicrosoftNETCoreAppRuntimeVersion) $(_HelixFriendlyNameTargetQueue) $(TargetArchitecture) $(RunQuarantinedTests) $(DotnetEfPackageVersion) Microsoft.AspNetCore.App.Runtime.win-x64.$(AppRuntimeVersion).nupkg Microsoft.AspNetCore.App.Ref.$(AppRuntimeVersion).nupkg $(HelixTimeout)</Command> | |||
<Command Condition="!$(IsWindowsHelixQueue)">./runtests.sh $(TargetFileName) $(NETCoreSdkVersion) $(MicrosoftNETCoreAppRuntimeVersion) $(_HelixFriendlyNameTargetQueue) $(TargetArchitecture) $(RunQuarantinedTests) $(DotnetEfPackageVersion) Microsoft.AspNetCore.App.Runtime.win-x64.$(AppRuntimeVersion).nupkg Microsoft.AspNetCore.App.Ref.$(AppRuntimeVersion).nupkg $(HelixTimeout)</Command> | |||
<Command Condition="$(IsWindowsHelixQueue)">call runtests.cmd $(TargetFileName) $(MicrosoftNETCoreAppRuntimeVersion) $(_HelixFriendlyNameTargetQueue) $(TargetArchitecture) $(RunQuarantinedTests) $(DotnetEfPackageVersion) Microsoft.AspNetCore.App.Runtime.win-x64.$(AppRuntimeVersion).nupkg Microsoft.AspNetCore.App.Ref.$(AppRuntimeVersion).nupkg $(HelixTimeout)</Command> |
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.
Suggestion: Typically this would be expressed like:
Condition=" '$(IsWindowsHelixQueue)' == 'true' ">
or Condition=" '$(IsWindowsHelixQueue)' != 'true' ">
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.
@MattGal that's true when the property defaults to empty. But, when a property is always set to true
or false
, using it directly as a bool
is easier to read and 💯% supported in msbuild
and dotnet msbuild
.
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.
aspnetcore/eng/targets/Helix.props
Lines 17 to 18 in 324a900
<IsWindowsHelixQueue>false</IsWindowsHelixQueue> | |
<IsWindowsHelixQueue Condition="$(HelixTargetQueue.Contains('Windows')) or $(HelixTargetQueue.Contains('windows'))">true</IsWindowsHelixQueue> |
👀 |
@MattGal @pranavkm