CumulusCI
CumulusCI helps build great applications on the Salesforce platform by automating org setup, testing, and deployment for everyone --- from developers and admins to testers and product managers.
Best practices, proven at scale. CumulusCI provides a complete development and release process created by Salesforce.org to build and release applications to thousands of users on the Salesforce platform. It's easy to start new projects with a standard set of tasks (single actions) and flows (sequences of tasks), or customize by adding your own.
Batteries included. Out-of-the-box features help you quickly:
- Build sophisticated orgs with automatic installation of dependencies.
- Load and capture sample datasets to make your orgs feel real.
- Apply transformations to existing metadata to tailor orgs to your specific requirements.
- Run builds in continuous integration systems.
- Create end-to-end browser tests and setup automation using Robot Framework.
- Generate synthetic data on any scale, from a single record to a million, using Snowfakery.
Build anywhere. Automation defined using CumulusCI is portable. It is stored in a source repository and can be run from your local command line, from a continuous integration system, or from a customer-facing MetaDeploy installer. CumulusCI can run automation on scratch orgs created using the Salesforce CLI, or on persistent orgs like sandboxes, production orgs, and Developer Edition orgs.
Learn more
For a tutorial introduction to CumulusCI, complete the Build Applications with CumulusCI trail on Trailhead.
To go in depth, read the full documentation.
If you just want a quick intro, watch these screencast demos of using CumulusCI to configure a Salesforce project from a GitHub repository.
For a live demo with voiceover, please see Jason Lantz's PyCon 2020 presentation from minute 36 through minute 54.
Questions?
Ask in the CumulusCI (CCI) group in the Trailblazer Community.
Please note: CumulusCI is distributed under an open source license and is not covered by the Salesforce Master Subscription Agreement.
v4.11.0 (2026-10-30)
What's Changed
Critical Changes
- Support PKCE and refresh token rotation for connected app logins by @sf-brahm-gaur in #4013
Changes
- docs(contributing): switch local setup to uv and add UTC test note by @sf-brahm-gaur in #4011
Full Changelog: https://github.com/SFDO-Tooling/CumulusCI/compare/v4.10.1...v4.11.0
3 maintainers
Metadata
3 maintainers
Release files for cumulusci 4.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cumulusci-4.11.0.tar.gz | 1.1 MB | Without provenance | Details for cumulusci-4.11.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cumulusci-4.11.0-py3-none-any.whl | Python 3 | none | any | Details for cumulusci-4.11.0-py3-none-any.whl |
Total release size: 2.5 MB
Release files / cumulusci-4.11.0.tar.gz
| Download URL | cumulusci-4.11.0.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c24af61d325ddb751f8f9df2a44d0e2b0dd59338e599cfcb13fcda520b096e25
|
|
BLAKE2b-256 checksum How to use checksums |
b51524e77537030748a34ae75ce2dbad18536e9ef8b35b8ebb43f8ad2087612d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.18.2 {"ci":true,"cpu":"x86_64","distro":{"id":"noble","libc":{"lib":"glibc","version":"2.39"},"name":"Ubuntu","version":"24.04"},"implementation":{"name":"CPython","version":"3.13.17"},"installer":{"name":"hatch","version":"1.18.2"},"openssl_version":"OpenSSL 3.0.13 30 Jan 2024","python":"3.13.17","system":{"name":"Linux","release":"7.0.0-1017-azure"}} HTTPX2/2.16.0
|
Release files / cumulusci-4.11.0-py3-none-any.whl
| Download URL | cumulusci-4.11.0-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a49d50517696516b7782cda5da5192113d10af67768ff4300deaf2724aa56d85
|
|
BLAKE2b-256 checksum How to use checksums |
4e69e3a5b9d463658938e30572b7385b86900d87bd8f49c888b64471473fb706
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.18.2 {"ci":true,"cpu":"x86_64","distro":{"id":"noble","libc":{"lib":"glibc","version":"2.39"},"name":"Ubuntu","version":"24.04"},"implementation":{"name":"CPython","version":"3.13.17"},"installer":{"name":"hatch","version":"1.18.2"},"openssl_version":"OpenSSL 3.0.13 30 Jan 2024","python":"3.13.17","system":{"name":"Linux","release":"7.0.0-1017-azure"}} HTTPX2/2.16.0
|
Security for cumulusci 4.11.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
