Skip to main content

Azure Pipelines - Batching your CI builds

I’m a big fan of Continuous Integration and Trunk-based development. As a result during a normal day a lot of code is pushed to the trunk(master, main,… whatever you call it)  branch. Pushing changes to this branch will trigger a CI build.

Of course as a lot of changes are pushed during the day a lot of builds are triggered. If your build time is small this is ok, but when your build time starts to increase it can become  interesting to look at ways to improve this process.

A possible solution is to start batching your CI builds in Azure DevOps. By enabling batching no new CI build is triggered when a previous build is still in progress.

To explain this in a little more detail; this means when multiple changes are pushed with short intervals, only 2 CI builds will be triggered. One when the first change is pushed and one after the first CI build has completed(of course this all depends on the build time of your CI build and the exact interval between your pushes but you get the idea).

Enabling batching

To enable batching using the classic pipelines, you need to execute the following steps:

  • Edit your pipeline
  • Go to Triggers
  • Check the Batch changes while a build is in progress checkbox

This feature is also supported using the YAML pipelines, add the batch option to trigger and set it to true:

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.

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...

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Col...