Skip to main content

Azure DevOps Server - Switch from HTTP to HTTPS–Part 4

With the release of Azure DevOps Server 2022, I thought it would be a good time to finally make the switch to HTTPS for our internal Azure DevOps server. With the idea to minimize downtime, I decided to first introduce the HTTPS endpoint before upgrading the Azure DevOps server. But o boy, what I thought would be an easy task turned out to be quite a journey.

In part 1 I explained the steps that should be done at the server side, in part 2 I continued with an explanation of the changes done on the client side. In the third and what I thought would be the final part I had a look at the errors I got on the build server.

But here I'm back again with a fourth part, and yes I promise this will be the last one.

Although I thought I had fixed everything, I got another error when I tried to build an application(both in Visual Studio and through the Azure DevOps build pipeline). I first noticed the problem when building through Azure Pipelines, here is the error I got:

It seems that NuGet couldn’t find and restore the NuGet packages.

When I had a look at the beginning of the NuGet task it became quite obvious why:

The pipeline was still using the old http based Azure Artifact endpoint instead of the new https endpoint.

Ok, let’s see how we can fix this…

Updating the NuGet Package Source

If you got this error in your build pipeline, it probably means that you have configured your NuGet restore task with the ‘Feeds in my Nuget.config’ option:

As you know there are multiple ways you can specify the source of your NuGet packages and one of them is through a nuget.config file. Visual Studio will also use this file if it is found in your solution or project directory.

So to get rid of the error and be able to successfully restore our NuGet packages, we need to update our Nuget.config file to use our HTTPS endpoint:

Remark: Be aware that there is also a global Nuget.config file, it can be possible that you have your Package Source configured there. You can find this global Nuget.config file in the following location:

%AppData%\NuGet\NuGet.Config

If you need to update the list of Package Sources in Visual Studio, go to the Visual Studio Options --> NuGet Package Manager --> Package Sources and update the URL there:

 

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more