azure-devops-cli-extension

Azure DevOps Extension for Azure CLI

Runs with mockssource: GitHubhomepagePythonMITcommit 4d49a4b367fd

Python, MIT licensed. The project labels itself: agile, artifacts, azure, azure cli, azure cli extension, azure devops, azure devops extension and boards.

azure-devops-cli-extension runs, with stand-ins for the services it depends on. An Argusic agent installed it in 30 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.

Azure DevOps CLI extension 1.0.8 is installed and its `az devops` help launches, and 354 unit tests plus 8 integration scenarios run green against an in-process mock of the Azure DevOps REST API.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 84.3 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
84.3 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
2
last tested
stars
694
forks
284
open issues
339
watchers
35
size
7 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing azure-devops-cli-extension, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • VCR integration recordings reference old API URL shapes and replay fails against the current generated SDK30 minutes
  • Mock lacked correct semantics for work items (AreaPath project, id propagation, delete 404), refs filter, import request route variants, and policy endpoints15 minutes
  • SDK OPTIONS/cache route templates lacked project-scoped paths for git/wit/refs/imports, so URLs omitted the project segment10 minutes
  • dev_setup.py requirements omitted azure-cli-testsdk and msrestazure needed by the test suite5 minutes
  • azure-cli-testsdk uses inspect.getargspec which Python 3.12 removed5 minutes
  • 23 integration scenarios (pipelines, wiki, security, boards query/relation/area/iteration, team, user, invoke, PR policies/reviewers, variable groups) still fail against the mock
Install time
30 minutes
Cold machine to finish
68 minutes
Errors hit and fixed
6 hit, 5 fixed with no human help
How the result was proved
python -m pytest azext_devops/tests/latest --ignore=azext_devops/tests/latest/integrationtests -p conftest_for_mock -q exited 0 with '354 passed, 6 subtests passed'; python -m pytest azext_devops/tests/latest/integrationtests/test_reposRepoTest.py test_devopsProjectTest.py test_reposImportTest.py test_boardsWorkItemTest.py test_reposRefTest.py test_reposRefDeleteFlowTest.py test_extensionSearch.py test_gitAliasTest.py -p conftest_for_mock -q exited 0 with '8 passed'; az version printed azure-cli 2.91.0; az devops -h printed the group help; az extension list printed ['azure-devops']
Model tokens used
12,195,078
Exact commit tested
4d49a4b367fd
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Mission complete within the 90-minute budget. Final report:
- Install: `python scripts/dev_setup.py` succeeded; Azure CLI 2.91.0, extension `azure-devops 1.0.8…
- Tests: unit suite `354 passed, 6 subtests passed in 11.07s` (with the env-only mock plugin); 8 in…
- Troubleshooting recorded: missing `azure-cli-testsdk`/`msrestazure`, Python 3.12 `inspect.getargs…
- 23 integration scenarios remain red because they exercise API areas (pipelines/build/variable-gro…
tokens used
12,195,078
Mission complete within the 90-minute budget. Final report:
- Install: `python scripts/dev_setup.py` succeeded; Azure CLI 2.91.0, extension `azure-devops 1.0.8…
- Tests: unit suite `354 passed, 6 subtests passed in 11.07s` (with the env-only mock plugin); 8 in…
- Troubleshooting recorded: missing `azure-cli-testsdk`/`msrestazure`, Python 3.12 `inspect.getargs…
- 23 integration scenarios remain red because they exercise API areas (pipelines/build/variable-gro…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 30 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
  • Hit 6 errors during setup, 1 of which were not solved.

Of the 5 agile projects Argusic has installed and timed, azure-devops-cli-extension was the 5th fastest to reach a running state, and 4 of 5 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks88.670.14
Argusic Runner1/3Unverified80.000.02

Topics (from GitHub)

agileartifactsazureazure-cliazure-cli-extensionazure-devopsazure-devops-extensionboardscicdcommand-linecommand-line-tooldevopsgitpipelinesrepos

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/azure-devops-cli-extension.svg)](https://argusic.com/subject/azure-devops-cli-extension)

Questions

Does azure-devops-cli-extension run?
azure-devops-cli-extension runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 30 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test azure-devops-cli-extension?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4d49a4b367fd. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test azure-devops-cli-extension?
The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does azure-devops-cli-extension take to install?
30 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does azure-devops-cli-extension need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing azure-devops-cli-extension?
6 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does azure-devops-cli-extension compare with the alternatives?
Of the 5 agile projects Argusic has installed and timed, azure-devops-cli-extension was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for azure-devops-cli-extension?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion