-
Notifications
You must be signed in to change notification settings - Fork 361
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
Update the SDK to 6.0 Preview 1 #6975
Conversation
@mmitche any idea what's causing the failure? |
/azp run arcade-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
Had to update the NuGet package dependencies because of a breaking change in their API: NuGet/NuGet.Client#3215 (comment). |
/azp run arcade-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
This comment has been minimized.
This comment has been minimized.
Leunin proces. Syst.m 32 windows advanced instller |
Be happy het antwoorx op metox das metox!
Op za 20 feb. 2021 13:17 schreef azure-pipelines[bot] <
notifications@github.com>:
… Azure Pipelines successfully started running 1 pipeline(s).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6975 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQJF5LUM4ZRXJP66YIYQK4TS76R5NANCNFSM4X2SC5YA>
.
|
@dotnet/dnceng can someone please help me figuring out why the |
@ViktorHofer let me see |
@premun That's not the version of aspnetcore in preview 1 (is actually 6.0.0-preview.1.21103.6) |
So the problem is that XHarness is a .NET Core 3.1 tool and the version was hardcoded to 3.1.5. But then it was changed here: @steveisok I have only seen the other change where you require the aspnetcore-sdk instead of runtime if it's desired. Why did we need to also change the version? This SDK should be only used to run XHarness or there are other things like the web server in the WASM flows? |
That change may be getting rolled out to arcade here: #7005 |
The value gets set here:
If we have incoherent preview versions between the SDK and the ASP.NET Core version, we might need to have two variables then but I am not sure about the impact of a change like that. |
It's safe to assume that we will have incoherent versions for every preview, and coherent for any RTM/servicing version. |
@ViktorHofer how urgent is this update? I am a bit burried this week but I could look into it next week |
It would be really great to get this in before Monday 3/1 which is the date when we update the SDK in dotnet/runtime as part of our batched rollout. |
I will have a look on Friday then. I need to make sure a change here won't cause problems down the line first so I don't want to rush it much. But please be aware that this probably only changes which .NET we use to build Arcade. The projects themselves have only recently been updated to .NET Core 3.1 (#6891). So the produces of Arcade are behind quite a lot. |
That is understood and expected. Even though I think we should always build against latest, the reason why this PR is opened is to flow the SDK update to 6.0 P1 into all "arcadified" repositories. Arcade handles that well as its part of the Maestro dependency flow. |
As agreed in Tactics, we want to dogfood our own SDK builds on a monthly cadence. Also sent out a mail to tactics for approval.
a890f2f
to
870e770
Compare
So I actually found that the real problem is different.. /__w/1/s/src/Microsoft.DotNet.Helix/Sdk/tools/dotnet-cli/DotNetCli.targets(5,5): Unable to find dotnet cli aspnetcore-runtime version 6.0.0-preview.1.21102.12, tried https://dotnetcli.azureedge.net/dotnet/aspnetcore/Runtime/6.0.0-preview.1.21102.12/aspnetcore-runtime-6.0.0-preview.1.21102.12-osx-x64.tar.gz [/__w/1/s/tests/UnitTests.XHarness.iOS.proj] |
Adding @mairaw for dot.net. As per the release.json, the ASP.NET Runtime version is 6.0.0-preview.1.21103.6 while runtime version is 6.0.0-preview.1.21102.12. Also releases.json has the correct URL for aspnetcore-runtime-osx-x64 |
Thanks! So I guess the way we get the URL is wonky in our case:
I guess we should be parsing the |
@ViktorHofer the build is green now but it forces the specific preview version in a sort-of hacky way. Nonetheless, it should work since it's tied to SDK version set in @mmitche thoughts? |
Yep fine by me. Parsing the releases.json seems questionable. There are times when we don't use officially released versions here. |
Yes works for me too. Let's just make sure that the proper fix gets the right attention after this is in. Thanks to all that helped getting this in. |
Thanks for the ping @rbhanda. I've fixed the download page info: |
* Update the SDK to 6.0 Preview 1 As agreed in Tactics, we want to dogfood our own SDK builds on a monthly cadence. Also sent out a mail to tactics for approval. * Remove default for ASP.NET Core runtime SDK * Hardcode the preview version to unblock ourselves * Force the Preview 1 version even more * Override inside of the XHarness SDK Co-authored-by: Premek Vysoky <premek.vysoky@microsoft.com>
As agreed in Tactics, we want to dogfood our officially released SDK builds on a monthly cadence. Also sent out a mail to tactics for approval.
To double check: