azure-pipelines-agent VS actions-runner-

> GitHub Actions is based on Visual Studio Team Foundation Server's CI, and later Azure DevOps

Yes and no, ADO Agent (https://github.com/microsoft/azure-pipelines-agent) is far more secretive and "black-box" alike.

Fun fact: Microsoft had a plan to provide that!

They canned it.

https://github.com/microsoft/azure-pipelines-agent/pull/2687...

You will need to download the agent (https://github.com/microsoft/azure-pipelines-agent/releases/latest ) and run the configure command.

A GitHub issue was opened to track support for different Node versions with custom tasks, but it remained unresolved for a long time. In October 2022 it was announced that Node.js 16 support was available.

Even thought im in the EU datacenter, my hosted agent is version 2.213.2, which is also the latest version of the agent taht was released by MS - https://github.com/microsoft/azure-pipelines-agent

{ "name": "AzurePipelines", "dockerFile": "Dockerfile", // Configure tool-specific properties. "customizations": { // Configure properties specific to VS Code. "vscode": { // Add the IDs of extensions you want installed when the container is created. "extensions": [ "ms-vscode.azurecli", "ms-vscode.powershell", "hashicorp.terraform", "esbenp.prettier-vscode", "tfsec.tfsec" ] } }, // Use 'forwardPorts' to make a list of ports inside the container available locally. // "forwardPorts": [], // Use 'postStartCommand' to run commands each time the container is successfully started.. "postStartCommand": "/home/vscode/azure-pipelines/start.sh", // Comment out to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. "remoteUser": "vscode", // Amend Azure Pipelines agent version and arch type with 'ARCH' and 'AGENT_VERSION'. https://github.com/microsoft/azure-pipelines-agent/releases. "build": { "args": { "UPGRADE_PACKAGES": "true", "ARCH": "x64", "AGENT_VERSION": "2.206.1" } }, "features": { "terraform": "latest", "azure-cli": "latest", "git-lfs": "latest", "github-cli": "latest", "powershell": "latest" } }

Looks like they are working on it:https://github.com/microsoft/azure-pipelines-agent/issues/3922

Thanks for sharing this. As mentioned in this GitHub issue, the build pipeline does render PS 7.2 new color escape sequences, however release pipeline does not.

had the exact same thing with https://github.com/actions-runner-controller/actions-runner-...

It's not official, but there are K8s / github actions runner deployments: https://github.com/actions-runner-controller/actions-runner-...

I've been playing about with this and it seems to work quite well. Startup latency is quite high, and it's one pod-per-job (I think), but seems pretty flexible.

We use https://github.com/actions-runner-controller/actions-runner-... to auto scale on EKS. It also allows you to use a GitHub App for the runner registration instead of personal access tokens. Also it seems like the project is receives support from GitHub because they’re getting early access to test out features.