powerplatform-build-tools

Power Platform Build Tools automate common build and deployment tasks related to Power Platform. This includes synchronization of solution metadata (a.k.a. solutions) between development environments and source control, generating build artifacts, deploying to downstream environments, provisioning/de-provisioning of environments, and the ability to perform static analysis checks against your solution using the PowerApps checker service.

Runs with mockssource: GitHubTypeScriptMITcommit 6e6fea90d7d1

TypeScript, MIT licensed. The project labels itself: azure devops, azure devops extension, ci cd, dataverse and powerplattform.

powerplatform-build-tools runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The project compiles successfully via webpack and all 126 unit tests pass. Component and functional tests are gated behind real Power Platform credentials (PA_BT_ORG_PASSWORD) which are not available in this container.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
313
forks
71
open issues
240
watchers
32
size
5 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 powerplatform-build-tools, 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.

  • npm install failed with E401 - @microsoft/powerplatform-cli-wrapper requires GitHub Packages auth4 minutes
  • gulp compile crashed with JavaScript heap OOM (2GB default limit exceeded by webpack)1 minute
  • Functional and component tests require PA_BT_ORG_PASSWORD env var (Power Platform credentials)
Install time
7 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
node --max-old-space-size=8192 node_modules/gulp/bin/gulp.js test exited 0, unitTest: 126 passing, 19 pending; functionalTest skipped: requires PA_BT_ORG_PASSWORD
Model tokens used
205,285
Exact commit tested
6e6fea90d7d1
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

The end of the recording

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

checker
copy-environment
create-environment
delete-environment
total 4
drwxrwxr-x  3 runner runner   32 Oct 25 07:21 .
drwxrwxr-x 36 runner runner 4096 Oct 25 07:21 ..
drwxrwxr-x  2 runner runner   30 Oct 25 07:21 export-solution-v2
Here's the complete assessment:
tokens used
205,285
Here's the complete assessment:

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

  • Installed in 7 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

azure-devopsazure-devops-extensionci-cddataversepowerplattform

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/powerplatform-build-tools.svg)](https://argusic.com/subject/powerplatform-build-tools)

Questions

Does powerplatform-build-tools run?
powerplatform-build-tools runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test powerplatform-build-tools?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6e6fea90d7d1. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test powerplatform-build-tools?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does powerplatform-build-tools take to install?
7 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 powerplatform-build-tools need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing powerplatform-build-tools?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for powerplatform-build-tools?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion