Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Report bugs at https://github.com/SFDO-Tooling/CumulusCI/issues.
When reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whomever wants to implement it.
Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whomever wants to implement it.
CumulusCI could always use more documentation, whether as part of the official CumulusCI docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue at https://github.com/SFDO-Tooling/CumulusCI/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Ready to contribute? Here's how to set up CumulusCI for local development.
Fork the CumulusCI repo on GitHub.
Clone your fork to your local workspace.
Create a fresh virtual environment using virtualenv and install development requirements:
$ pip install -r requirements_dev.txt
Install
pre-commithooks forblackandflake8:$ pre-commit install --install-hooks
After making changes, run the tests and make sure they all pass:
$ pytest
Your new code should also have meaningful tests. One way to double check that your tests cover everything is to ensure that your new code has test code coverage:
$ make coverage
Push your changes to GitHub and submit a pull request. The base branch should be a new feature branch that we create to receive the changes (contact us to create the branch). This allows us to test the changes using our build system before merging to master.
Note that we enable typeguard with pytest so if you add type declarations to your code, those declarations will be treated as runtime assertions in your python tests. MyPy validation is also on our roadmap.
Before you submit a pull request, check that it meets these guidelines:
- Documentation is updated to reflect all changes.
- New classes, functions, etc have docstrings.
- New code has comments.
- Code style and file structure is similar to the rest of the project.
- You have run the black code formatter.
It's easy to release a version of CumulusCI to GitHub and PyPI! First, create a new branch for your version:
$ git checkout -b feature/newversionMake the necessary changes to prepare the new release:
- Update the version in
cumulusci/version.txt- Update the release notes in
HISTORY.rst. Information in our project history is derived from Pull Request notes found in GitHub and dating back to our previous release.
Commit the changes, open a Pull Request on GitHub and request approval from another committer. Once your PR has been merged, a GitHub action will automatically create the release tag and push the artifacts to PyPI.
After a couple minutes, check for the new release's appearance at https://pypi.org/project/cumulusci/
Next, head to the tag that was autocreated in the GitHub repository and edit it. Populate the version number and paste in the changelog notes from HISTORY.rst. Note that some formatting, such as reStructuredText links, need to be converted to Markdown. Publish the release.
You can then create a pull request to update the Homebrew Tap by running this locally (note, it's important to do this as soon as possible after the release is published on PyPI, because PyPI is the source CumulusCI checks to see if a new version is available):
$ git checkout master
$ git pull
$ make release-homebrewNote
The release-homebrew build step depends on the jq command line utility which is available via Homebrew.
That will create a new pull request in the SFDO-Tooling/homebrew-sfdo repository, which can be merged if its tests pass.
Finally, post the release notes to our usual channels:
- CumulusCI Release Announcements group in the Power of Us Hub https://powerofus.force.com/s/group/0F91E000000DHjTSAW/cumulusci-release-announcements
- CumulusCI group in the Trailblazer community https://success.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F9300000009M9ZCAU
Some tests are marked @pytest.mark.vcr() which means that they can either
call into a real (configured) Salesforce org or use a cached YAML file of the request/response.
To regenerate the VCR file, you can run pytest like this:
$ pytest cumulusci/.../test_<something>.py --org <orgname>Where "orgname" is a configured org name like "qa", "dev", etc.
Periodically you can also do this, but it will take a LONG time:
$ pytest --org <orgname>That will run all VCR-backed tests against the org, including all of the slow integration tests.
Some of these tests generate so much data or run so slowly that even the VCR tool does not help much. For example, if you are testing something that needs to download an entire org schema.
These tests can be marked with @pytest.mark.integration_test(). In that case,
you can invoke them the same way as above, but you should not check in their
YAML file into the repo. One of our files generates more than 300MB of cache data.
You can invoke these tests the same way:
$ pytest cumulusci/.../test_<something>.py --org qaThis will generate the cached data.
Later, you can use the cached data like this:
$ pytest cumulusci/.../test_<something>.py --accelerate-integration-testsIt will usually be much faster than calling into the Salesforce org, but it will still be quite slow compared to normal unit tests. Nevertheless, if you are changing feature tested by these tests, you should run them periodically.
Do not commit the files ("large_cassettes/*.yml") to the repository.