Skip to main content

Azure DevOps–Nuget package caching

By default when you build your project in Azure DevOps pipelines, any package dependencies will be restored as part of the build process. Of course if you have a large list of packages, this can take a long time. Let’s see how we can reduce build time by using Nuget package caching

Lock dependencies using package.lock.json

Before we can use the cache task, we need to lock our project’s dependencies. This is done through a package.lock.json file that will be used to generate a unique key for our cache.

We don’t have to create this package.lock.json file ourselves but we can tell msbuild to generate it when building our project by setting the RestorePackagesWithLockFile property to true:

Don’t forget to check your packages.lock.json file into your source code.

Update our Azure DevOps Pipeline

Now we need to update our Azure DevOps pipeline to use the Cache task. This task will use the content of the packages.lock.json to produce a dynamic cache key. This will ensure that every time the file is modified, a new cache key will be generated.

The cache task will set the CACHE_RESTORED variable to true when we have a cache hit. Now we can use this variable in our NuGet restore task to only run this when the CACHE_RESTORED variable is false:

What about Azure DevOps Server?

Important to know is that this feature only works on Azure DevOps in the cloud and not on the on-premise version. Although it is possible to add the Cache task to your pipeline, you will get an error once you try to invoke the pipeline:

Information, Getting a pipeline cache artifact with the following fingerprint: `nuget|"Windows_NT"|YSCGwKQO4VRcWyDWNaFykEpIXXbRcTAlRukqsPhvvaA=`.

##[error]API resource location a7c78d38-31a8-417e-ba6b-7e58b352f304 is not registered on https://servername/tfs/DefaultCollection/.

Finishing: Cache

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more