CumulusCI
Python framework for building portable automation for Salesforce projects
Runssource: GitHubhomepagePythonBSD-3-Clausecommit 38a6b1b5ff08
Python, BSD-3-Clause licensed. The project labels itself: cicd, continuous integration, github, salesforce, salesforce apex, salesforce api, salesforce developers and salesforce devops.
CumulusCI runs. An Argusic agent installed it in 0.8 minutes and hit 7 errors on a clean machine with no GPU, and the whole session was recorded.
CLI installed and responds correctly; 3231 unit tests pass; 2 VCR-based Salesforce upsert tests fail due to cassette format incompatibility with vcrpy 8.x that requires re-recording against a live Salesforce org
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 97.1 of 100 (the mean of this project's run scores).
At a glance
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- VCR cassettes for upsert tests incompatible with vcrpy 8.x (CannotOverwriteExistingCassetteException)10 minutes
- vcrpy 8.x passes bytes_iterator/list-of-bytes for request bodies, _cleanup/simplify_body expects bytes8 minutes
- LibraryDocBuilder/ResourceDocBuilder missing doc_format arg (Robot Framework 7.x breaking change)5 minutes
- MockHttpResponse sub-mock creation fails with unexpected kwarg 'parent' (Python 3.12 unittest.mock)5 minutes
- Back-compat test subprocess fails due to ImportPathMismatchError with installed cumulusci package4 minutes
- Salesforce PATCH tests fail with ChunkedEncodingError (urllib3 2.x rejects body on 204)3 minutes
- Install time
- under a minute
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 7 hit, 6 fixed with no human help
- How the result was proved
- cci version exited 0 (v4.10.1); pytest --tb=line -q produced 3231 passed, 37 skipped, 2 failed, 3 subtests passed
- Model tokens used
- 779,595
- Exact commit tested
- 38a6b1b5ff08
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
FAILED cumulusci/tasks/bulkdata/tests/test_upsert.py::TestUpsert::test_upsert_complex_fields__bulk 2 failed, 3231 passed, 37 skipped, 4991 warnings, 3 subtests passed in 83.33s (0:01:23) === CLI Version === CumulusCI version: 4.10.1 (/tmp/cci-venv/bin/cci) Python version: 3.12.3 (/tmp/cci-venv/bin/python3.12) === Total tests === -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 3270 tests collected in 2.24s Here is my compiled final report: tokens used 779,595 Here is my compiled final report:
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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.8 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Hit 7 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.8 minutes after the clone.
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
Topics (from GitHub)
cicdcontinuous-integrationgithubsalesforcesalesforce-apexsalesforce-apisalesforce-developerssalesforce-devopssalesforce-isv-developersalesforce-metadatasalesforcedxsfdx
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cumulusci)Questions
- Does CumulusCI run?
- Yes. CumulusCI runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test CumulusCI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 38a6b1b5ff08. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test CumulusCI?
- The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does CumulusCI take to install?
- 0.8 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 CumulusCI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing CumulusCI?
- 7 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for CumulusCI?
- 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.