Skip to main content

Azure DevOps Pipelines–Ignore build trigger for specific paths

Last week a colleague complained to me that he had to wait for an available build agent on our Azure DevOps build server. The reason that all build agents were busy was because I was doing a lot of changes to the documentation(also stored in an Azure DevOps Git repository) causing a lot of builds to be triggered resulting in long wait queues.

As only changing the markdown files in the wiki doesn’t need a build to be created, he asked me to configure the build trigger to ignore documentation changes.

Let me show you how to configure this…

Classic Pipelines

To configure this for the ‘classic’ pipelines in Azure DevOps, you need to go to the Triggers tab for your pipeline. There you’ll find a Path filters section on the right where you can specify specific paths to include or exclude.

In our example, we want to exclude everything inside the ‘SOFACore/Docs’ folder:

 


YAML Pipelines

If you are using a YAML pipeline, you need to edit the trigger section and add a path exclude there:

 

That’s it!

More information

Build Azure Repos Git repositories - Azure Pipelines | Microsoft Learn

Labels:

Popular posts from this blog

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

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