I have a long stable Azure DevOps pipeline to deploy a .NET core application, and in one of the Agent Jobs I have some tasks to deploy (drop and recreate) some databases using dotnet ef
commands.
This release pipeline has been working smoothly from months now.
I am explicitly using .NET Core SDK 2.2 in the Agent Job, so the first task of the Agent Job is to install SDK 2.2.100. This Agent Job runs on a Hosted Windows 2019 with VS2019 agent pool.
The problem is that a couple of days ago (Sep 27) the dotnet restore
task I'm using before the dotnet ef
commands, suddenly started to use .NET Core SDK 3.0, breaking my pipeline, since dotnet ef command-line tool is not included anymore as a part of the SDK. There was no change on the code related to that, nor in the pipeline, so I guess something changed on Microsoft side.
Before:
After:
I managed to patch the issue adding a new task to install the EF tools (dotnet update --global dotnet-ef
), but this is a just a patch. I need to understand the root cause of the error so I can understand if there's something wrong with my pipeline or with my solution-
Does anyone know what happened here, or anyone can help me to fix my pipeline to force it to use SDK 2.2 instead of SDK 3.0 as it should be?