Skip to content

Install .NET Core 3.1 SDK on Windows to support Track 1 SDK#35151

Merged
live1206 merged 8 commits intoAzure:mainfrom
live1206:fix-track1-ci
Apr 7, 2023
Merged

Install .NET Core 3.1 SDK on Windows to support Track 1 SDK#35151
live1206 merged 8 commits intoAzure:mainfrom
live1206:fix-track1-ci

Conversation

@live1206
Copy link
Member

@live1206 live1206 commented Mar 27, 2023

.NET Core 3.1 SDK does not exist on Windows hosted machine anymore, we still need it for Track 1 SDK
https://github.com/Azure/azure-sdk-for-net/pull/35148/checks?check_run_id=12290486264

Contributing to the Azure SDK

Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.

For specific information about pull request etiquette and best practices, see this section.

@live1206 live1206 changed the title Install .NET Core 3.1 SDK on Windows to support Track 1 Install .NET Core 3.1 SDK on Windows to support Track 1 SDK Mar 27, 2023
@live1206
Copy link
Member Author

@weshaggard Could you help to review this? Thanks!

@jsquire
Copy link
Member

jsquire commented Mar 27, 2023

@live1206: Please help me understand why we need a runtime that has reached end-of-life and is no longer supported. What libraries are failing and what target are they using?

//fyi: @heaths

Copy link
Member

@jsquire jsquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking merge until the scenario is understood.

@weshaggard
Copy link
Member

@live1206 I thought we were rolling forward to the latest .NET when running the code generation so why would we still need this? Is there something else that needs it?

Looking at your link it appears as though there are still some test projects targeting .NET Core 3.1. We should instead update those test projects to .NET 7.0 as .NET 3.1 is out support.

@benbp
Copy link
Member

benbp commented Mar 27, 2023

If this is indeed not necessary, I have a PR to remove the step entirely as we don't need to be wasting time on windows jobs installing it: #35174

@live1206
Copy link
Member Author

@live1206 I thought we were rolling forward to the latest .NET when running the code generation so why would we still need this? Is there something else that needs it?

Looking at your link it appears as though there are still some test projects targeting .NET Core 3.1. We should instead update those test projects to .NET 7.0 as .NET 3.1 is out support.

Tried with a draft PR #35178, it takes more effort than expected.
Basically a follow-up of #32814

@jsquire
Copy link
Member

jsquire commented Mar 28, 2023

Tried with a draft PR #35178, it takes more effort than expected. Basically a follow-up of #32814

There's a difference between building with the .NET 7 SDK and changing the target frameworks for libraries. We need to do the former, we do not want to do the latter.

@live1206 - would you please help us understand what problem you're trying to solve? What behavior are you seeing that requires changes?

@live1206
Copy link
Member Author

live1206 commented Mar 29, 2023

https://github.com/Azure/azure-sdk-for-net/pull/35148/checks?check_run_id=12290486264

@jsquire As I mentioned in the description, the CI is failing for Track 1 .NET SDK PR: https://github.com/Azure/azure-sdk-for-net/pull/35148/checks?check_run_id=12290486264, it is blocking Track 1 .NET SDK release. The reason the Track 1 CI failure is the Track 1 tests are requiring .NET core 3.1 during the run.

@jsquire
Copy link
Member

jsquire commented Mar 29, 2023

@jsquire As I mentioned in the description, the CI is failing for Track 1 .NET SDK

What should change here is the SDK in use; these should be compiled using the .NET 7 SDK. We do not want to install/use the .NET Core 3.1 SDK, as it has reached end-of-life.

@live1206
Copy link
Member Author

@jsquire As I mentioned in the description, the CI is failing for Track 1 .NET SDK

What should change here is the SDK in use; these should be compiled using the .NET 7 SDK. We do not want to install/use the .NET Core 3.1 SDK, as it has reached end-of-life.

As I explained in #35178 (comment), it's not an easy fix to upgrade the target .NET to latest.

@jsquire jsquire dismissed their stale review April 4, 2023 13:43

Dismissing block as a path forward has been agreed upon to unblock the release and address the underlying dependency issue in the longer term.

@weshaggard
Copy link
Member

/azp run net - mgmt

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@weshaggard
Copy link
Member

I'd like to make sure we get a test run of the mgmt pipeline as well to ensure this change works as expected.

@weshaggard
Copy link
Member

/azp run net - mgmt - ci

@azure-pipelines
Copy link

Azure Pipelines failed to run 1 pipeline(s).

@live1206
Copy link
Member Author

live1206 commented Apr 6, 2023

/azp run net - mgmt - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@live1206 live1206 merged commit d1b08d9 into Azure:main Apr 7, 2023
@live1206 live1206 deleted the fix-track1-ci branch April 7, 2023 00:47
linugeorgeofficial pushed a commit to linugeorgeofficial/azure-sdk-for-net that referenced this pull request Apr 11, 2023
)

* Install .NET Core 3.1 SDK on Windows to support Track 1

* Comment

* Install dotnet with tasks instead of template

* Install .net core 3.1 for Track 1 .NET SDK

* Remove condition

* Install .net core 3.1 for test as well
grizzlytheodore pushed a commit that referenced this pull request Apr 19, 2023
…rEnabled in SDK (#35466)

* Generated SDK and Added test

* Install .NET Core 3.1 SDK on Windows to support Track 1 SDK (#35151)

* Install .NET Core 3.1 SDK on Windows to support Track 1

* Comment

* Install dotnet with tasks instead of template

* Install .net core 3.1 for Track 1 .NET SDK

* Remove condition

* Install .net core 3.1 for test as well

---------

Co-authored-by: Wei Hu <live1206@gmail.com>
ArcturusZhang pushed a commit that referenced this pull request Apr 20, 2023
* generated with 2023-03-01 tag

* update version

* new recordings for all tests

* sanitize key

* last test recording

* Add test for VMSS Reapply (#34738)

* Add test for VMSS Reapply

* Record test

* Adding $expand query param as part of ListAll VMs in RG and Subscription (#34878)

* Adding $expand query param as part of ListAll VMs in RG and Subscription

* Record new test

---------

Co-authored-by: Theodore Chang <thchan@microsoft.com>

* Add VM property (#34842) (#34938)

Co-authored-by: payalguptapg <126145083+payalguptapg@users.noreply.github.com>
Co-authored-by: Theodore Chang <theodore.l.chang@gmail.com>

* Remove <br> syntax from most CRP swagger descriptions (#35016)

* br cleanup for net

* Update AutomaticOSUpgradePolicy.cs

* Update AutomaticOSUpgradePolicy.cs

* Add Compute SecurityPosture SDK for 2023-03-01 (#35345)

* Adding Restore Point Encryption, HyperVGeneration and WriteAcceleratorEnabled in SDK (#35466)

* Generated SDK and Added test

* Install .NET Core 3.1 SDK on Windows to support Track 1 SDK (#35151)

* Install .NET Core 3.1 SDK on Windows to support Track 1

* Comment

* Install dotnet with tasks instead of template

* Install .net core 3.1 for Track 1 .NET SDK

* Remove condition

* Install .net core 3.1 for test as well

---------

Co-authored-by: Wei Hu <live1206@gmail.com>

* Add sdk support for vmss deallocate hibernate optional parameter (#35335)

* dedicated host Resize (#35197)

Co-authored-by: Theodore Chang <thchan@microsoft.com>

* Adding missing property for VirtualMachineExtension and VMSSExtension (#35233)

* adding property

* Adding provisionedAfterExtensions in VirtualMachineExtension

* reverting the commit

* VMSSExtension

* added scenario test and record

* Reverting back files related to VirtualMachineScaleSetExtension.
Changes in VirtualMachineScaleSetVMExtension including adding scenario tests and record.

---------

Co-authored-by: Younghyun Kim <younghyunkim@microsoft.com>

* regenerated, metatags

* customizations

* sanitized SAS recordings for compliance CI

* finish customization. resolve build failure

---------

Co-authored-by: Theodore Chang <theodore.l.chang@gmail.com>
Co-authored-by: Anshul Verma <88476874+AnshulVermaa@users.noreply.github.com>
Co-authored-by: Kartik Gupta <31189137+Kartik-715@users.noreply.github.com>
Co-authored-by: payalguptapg <126145083+payalguptapg@users.noreply.github.com>
Co-authored-by: Adam Sandor <adsandor@microsoft.com>
Co-authored-by: mabhard <52765900+mabhard@users.noreply.github.com>
Co-authored-by: Linu George <127192938+linugeorgeofficial@users.noreply.github.com>
Co-authored-by: Wei Hu <live1206@gmail.com>
Co-authored-by: vatsan28 <vatsan9228@gmail.com>
Co-authored-by: cakarata <47228825+cakarata@users.noreply.github.com>
Co-authored-by: younghyun5756 <102988755+younghyun5756@users.noreply.github.com>
Co-authored-by: Younghyun Kim <younghyunkim@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.

4 participants