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

Labels:

Popular posts from this blog

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

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

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...
Read more