[plugin] Azure Devops

[robertbissonnette]

My org uses azure devops to handle CI this solution if it supported AZDO would be highly useful to keep our required number of macs on hand to a minimum.

The azure devops agent comes in 2 flavors:

• pipelines
• vsts-agent

vsts-agent contains legacy node for use with extensions requiring it, pipelines does not.

I've provided some starter scripts as part of issue, my org only cares about Arm64 so an enhancement to handle the x86_64 based macs via uname will be required should you use.

We parse the body off the latest release via the api, and extract out via pattern matching the proper version to download. We validate the sha256 checksum from the page after downloading the file. Parsing was originally done 100% in bash, but due to the differences in bash =~ operand in macos vs linux was changed to a powershell scriptlet.
Human Readable - https://github.com/microsoft/azure-pipelines-agent/releases
Machine - https://api.github.com/repos/microsoft/azure-pipelines-agent/releases

The script has AGENT_TYPE defined in it, the two valid values would be either pipelines-agent or vsts-agent

I have not included the script used to setup as a service as not sure that would be applicable here. I have not created a remove agent script from org yet either.

File: .env /.env.secret

AGENT_INSTALL_DIR=~/build-agent/

GITHUB_API_PAT=USER_PROVIDED
VSTS_AGENT_INPUT_TOKEN=USER_PROVIDED

download-agent.sh.txt
parse-releases.ps1.txt
configure-agent-clean.sh.txt
.capabilities.txt

The agent supports adding custom capabilities via a .capabilities file in ENV shell format if found in the install directory, it's not well documented but it is the approach that should be used for having the agent declare custom capabilities without user interaction on UI.

Reference links
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/osx-agent?view=azure-devops&tabs=IP-V4

[NorseGaud]

Planned for post-1.47.0 controller/registry release. @robertbissonnette would it be an issue if we schedule this out a few weeks? Or is there any sense of urgency/deal breaker situation for obtaining ephemeral VMs though your Anka setup?

[robertbissonnette]

@NorseGaud No rush needed, few weeks out is fine. We'll roll with non-ephemeral vms for a short period as needed.

[NorseGaud]

Hi @robertbissonnette , we're seriously sorry about the delay on this. We're making some major improvements to Anklet for Github Actions and we want to hold off on this so that we can design the Azure DevOps plugin with the new design and not have to write it twice. I expect the github actions plugin to be finished this week and us to start on Azure in at the very latest next week.

[NorseGaud]

Quick update: Azure Devops is... A bit rough...

• Jobs fail immediately for No agent found in pool anklet which satisfies the specified demands is there isn't an agent in the pool yet, so you have to connect at least one agent to the pool.
• The yaml uses pool and demands and I hope it's possible for us to collect these and use them to spin up an agent. Something like the below. If not, we may need to take an approach that's vastly different from github actions :(

pool:
  name: anklet
  demands:
    - "anka-template:84266873-da90-4e0d-903b-ed0233471f9f"
    - "anka-template-tag:6c14r"

[NorseGaud]

Not seeing a way to get the "demands" from the event posted to the receiver.

[NorseGaud]

Ok, so we'll need to call the API for the build ID to get the demands, but, it looks like there is a bug preventing it from showing: https://developercommunity.visualstudio.com/t/Azure-DevOps-REST-APIs:-Build-Definition/10827152?q=demands
https://developercommunity.visualstudio.com/t/Missing-Demand-object-from-Build-Rest/10509395

Fun :)

[NorseGaud]

Opened https://developercommunity.visualstudio.com/t/Demands-object-missing-from-buildsget-a/11024369 and the team at microsoft confirmed the bug. Waiting on a fix.