Skip to main content

Azure Pipelines- Agentless/Server jobs

While demonstrating some new Azure DevOps (TFS) functionalities to a customer, I got the following question; “What are agentless jobs?”.

Good question, let’s try to give an answer:

In Azure Pipelines there are 4 types of jobs:

  • Agent pool jobs run on an agent in an agent pool.
  • Server jobs run on the Azure DevOps server.
  • Container jobs run in a container on an agent in an agent pool.
  • Deployment group jobs run on machines in a deployment group. These jobs are only available in a release pipeline.

Our question is related to the second type of jobs; server jobs also known as agentless jobs.

Where most of the jobs are executed by a build agent, server jobs are executed directly on the Azure DevOps application server.  This means that a server job does not require an agent or any target computers.

Creating an agentless job

To create an agentless job, open up a build pipeline. Click on the … button at the pipeline level and choose Add an agentless job from the dropdown menu.

Now a new agentless job phase is added to your build pipeline.

Inside this phase, you can add tasks similar to the other phases.

Remark: Notice that only a limited set of tasks is supported in the Agentless job phase.

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