Azure DEVOPS Pipeline Incident in .NET 6 Migrations
Microsoft has been releasing .NET 6 improvements and SDKs one after another for a long time. We have been following these imrpovements closely in PEAKUP’s Velocity, Analytics and Data products for a long time. We take into account the performance-enhancing features in the latest SDKs and give a lot of importance to migrating projects to the latest version of .NET 6, . After the each Preview SDKthat has been released recently, we started to experience some glitches and outages in the DevOps pipeline. Today I’m going to tell you how we came across this little DevOps outage and how to fix it.
While developing our applications with .NET 6, we get them to work by hosting them in Azure Web Application. The expectation we have here is for the related SDK to be setup and be ready on the Web Application side after each SDK gets released, just like the SDK Container packages that are immediately reflected in the Microsoft Container Registry services.
However, the migrations of the Azure teams in the Microsoft 6.0.100-preview.7.21379.14 and 6.0.1-RC packages are quite surprising! Because, although a behavior that we specifically specified to use the latest version of 6 during the Build phase that we have built in DevOps Pipeline does not cause any errors in the Build and Release Pipeline, let us tell you that a very surprising problem awaits you once it is deployed to the application!
There is no RC package of .NET 6 in Azure Web Application! When you look at the DOTNET SDK list on Kudu SCM, you can see that the RC package is missing and the application tries to run for minutes without sending any Exceptions.
In order to solve this problem, it will be enough to specify the latest SDK version in the Azure Web Application specifically in the Pipeline!