Skip to content
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

Merged
merged 5 commits into from
Feb 25, 2021
Merged

Update the SDK to 6.0 Preview 1 #6975

merged 5 commits into from
Feb 25, 2021

Conversation

ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Feb 18, 2021

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:

@ViktorHofer ViktorHofer requested a review from mmitche February 18, 2021 16:06
@ViktorHofer
Copy link
Member Author

@mmitche any idea what's causing the failure?

@ViktorHofer
Copy link
Member Author

/azp run arcade-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ViktorHofer
Copy link
Member Author

Had to update the NuGet package dependencies because of a breaking change in their API: NuGet/NuGet.Client#3215 (comment).

@ViktorHofer
Copy link
Member Author

/azp run arcade-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Lodewijk1

This comment has been minimized.

@Lodewijk1
Copy link

Leunin proces. Syst.m 32 windows advanced instller

@Lodewijk1
Copy link

Lodewijk1 commented Feb 20, 2021 via email

@ViktorHofer
Copy link
Member Author

ViktorHofer commented Feb 23, 2021

@dotnet/dnceng can someone please help me figuring out why the FindDotNetCliPackage task is failing on the xHarness legs?

@premun
Copy link
Member

premun commented Feb 23, 2021

@ViktorHofer let me see

@mmitche
Copy link
Member

mmitche commented Feb 23, 2021

@premun That's not the version of aspnetcore in preview 1 (is actually 6.0.0-preview.1.21103.6)

@premun
Copy link
Member

premun commented Feb 23, 2021

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:
38a3674

@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?

@mmitche
Copy link
Member

mmitche commented Feb 23, 2021

That change may be getting rolled out to arcade here: #7005

@premun
Copy link
Member

premun commented Feb 23, 2021

The value gets set here:

<DotNetCliVersion Condition=" '$(DotNetCliVersion)' == '' AND '$(DotNetCliPackageType)' == 'runtime' ">$(BundledNETCoreAppPackageVersion)</DotNetCliVersion>
<DotNetCliVersion Condition=" '$(DotNetCliVersion)' == '' AND '$(DotNetCliPackageType)' == 'aspnetcore-runtime' ">$(BundledNETCoreAppPackageVersion)</DotNetCliVersion>

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.

@mmitche
Copy link
Member

mmitche commented Feb 23, 2021

The value gets set here:

<DotNetCliVersion Condition=" '$(DotNetCliVersion)' == '' AND '$(DotNetCliPackageType)' == 'runtime' ">$(BundledNETCoreAppPackageVersion)</DotNetCliVersion>
<DotNetCliVersion Condition=" '$(DotNetCliVersion)' == '' AND '$(DotNetCliPackageType)' == 'aspnetcore-runtime' ">$(BundledNETCoreAppPackageVersion)</DotNetCliVersion>

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.

@premun
Copy link
Member

premun commented Feb 24, 2021

@ViktorHofer how urgent is this update? I am a bit burried this week but I could look into it next week

@ViktorHofer
Copy link
Member Author

ViktorHofer commented Feb 24, 2021

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.

@premun
Copy link
Member

premun commented Feb 24, 2021

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.

@ViktorHofer
Copy link
Member Author

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.

ViktorHofer and others added 2 commits February 25, 2021 11:00
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.
@premun premun requested review from mmitche and riarenas February 25, 2021 14:18
@premun
Copy link
Member

premun commented Feb 25, 2021

So I actually found that the real problem is different..
The green version is in global.json and the yellow version it's trying to install but cannot find:

image

/__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]

@mmitche
Copy link
Member

mmitche commented Feb 25, 2021

@rbhanda @leecow See above, the included runtimes have the same version, but they're different for previews.

@rbhanda
Copy link

rbhanda commented Feb 25, 2021

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

@premun
Copy link
Member

premun commented Feb 25, 2021

Thanks!

So I guess the way we get the URL is wonky in our case:

"aspnetcore-runtime" => $"{DotNetCliAzureFeed}/aspnetcore/Runtime/{Version}/aspnetcore-runtime-{Version}-{Runtime}.{extension}",

I guess we should be parsing the release.json and getting it from there?

@premun
Copy link
Member

premun commented Feb 25, 2021

@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 global.json. If we want this in for Monday, I'd say we can do it and prepare a proper way to handle this.

@mmitche thoughts?

@mmitche
Copy link
Member

mmitche commented Feb 25, 2021

@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 global.json. If we want this in for Monday, I'd say we can do it and prepare a proper way to handle this.

@mmitche thoughts?

Yep fine by me. Parsing the releases.json seems questionable. There are times when we don't use officially released versions here.

@ViktorHofer
Copy link
Member Author

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.

@ViktorHofer ViktorHofer merged commit a6b570d into master Feb 25, 2021
@ViktorHofer ViktorHofer deleted the ViktorHofer-sdk6.0p1 branch February 25, 2021 23:35
@mairaw
Copy link

mairaw commented Feb 26, 2021

Thanks for the ping @rbhanda. I've fixed the download page info:
image

akoeplinger pushed a commit to akoeplinger/arcade that referenced this pull request Apr 12, 2021
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants