azure-pipelines-agent VS garden

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

Hey there! Have you tried garden.io for caching? We also cache tests. Pretty much anything that's possible to cache. We're open source at https://github.com/garden-io/garden

To add to what's already been said: If you think about it, CI pipelines are typically a complete description of how your system is built, tested, and deployed.

Which is pretty fantastic except for how walled off they are. You can't really re-use these descriptions for e.g. development, they're not vendor agnostic, and they only way to run them is by pushing your code.

Maybe it's a silly analogy but it's almost like being a web dev that doesn't have a browser and needs to send their code to a friend who can tell them if that font size looks good.

I think we're way over due for freeing these "blueprints" of our system from the confines of CI and making them portable and flexible. And containers are the technology that's enabling that.

Full disclaimer (as always): I work at Garden[0] where we're also solving that problem but taking a slightly different approach to Dagger (it's still a DAG). Garden config is declarative and the jobs (we call them actions) have a semantic meaning. You can e.g. have a Build action of type container or a Deploy action of type Helm and Garden will figure out what to do with it.

[0] https://github.com/garden-io/garden

Yes, there's us over at https://github.com/garden-io/garden! We're big believers in pipelines that run anywhere. I even made a short little video that should give you the gist. [1]

Some of the short-list of differences: we use YAML for our configuration language, Dagger can use full-fat languages to define its pipelines. Our feature scope is broader: you can use us to vend IDP-like stacks to your developers if you're a Platform Team; we make development with remote Kubernetes clusters very easy, including all the remote image builds; and we have a number of integrations so you can bring your IaC tool of choice (Pulumi, Terraform) into your pipeline and set up service -> infra dependencies.

[1] https://www.youtube.com/watch?v=JFnan6s2cDg

Me too. In fact Garden (dev tooling for the Kubernetes)[0] is a Berlin start-up with three Icelandic founders.

And if I'm not mistaken, two of us worked briefly with @halldorel (above commenter) at an earlier Icelandic start-up. It's a small world (if you're Icelandic).

[0] https://garden.io

There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com

Would appreciate any insights on garden.io. Thanks.

Telepresence, tilt, garden.io, okteto, skaffold etc.

- https://garden.io/

haha, do my pictures give off a strong not-web-dev vibe? Either way your right, I'm focusing on devxp and automation for kubernetes. Because my work is open source you can see it here https://github.com/garden-io/garden (btw we're also hiring another open core dev like me)