Configuration

To configure this module, you need to:

1. turn on Use buildouts on a repository
2. fill in a regex that allows to differentiate a normal branch name: For runbot, branches should be named $version-$sometext anyways, so this module's suggestion is to call buildout branches buildout-$version-$sometext
3. check the value of the field Buildout section, this must be the name you use in your buildouts
4. if you use multiple buildouts for the same version to implement some kind of DTAP scenario (you should), you can mark some buildout branch as the one to be used for tests by navigating to the repository and selecting a default buildout branch. In case you deal with multiple versions, set the default to a buildout from your current version, and set the buildout branch for branches of the new version manually
5. when converting a repository to use buildouts, be sure to remove all dependency branches first. Otherwise, runbot will copy all of them unnecessarily. Then, rebuild some buildout branch, and when it is green, rebuild another branch that is supposed to use the buildout

Background

This module will cause buildout branches to be treated radically differently: For buildout branches, the buildout will be run, and any failures reported in the build results. For normal branches, it will search for a buildout branch with a matching version, copy this buildout to a temporary directory, manipulate buildout.cfg to use the branch to be tested and the ports assigned for this instance, then rerun the buildout, then run tests within the buildout environment.

For this to work, your buildout.cfg needs to contain one addons line:

git $the_exact_repo_url_as_configured_in_runbot parts/$repo_name $version

or if you use pinned branches:

git $the_exact_repo_url_as_configured_in_runbot parts/$repo_name $commit_hash branch=$version

Which then will be replaced by:

git $the_exact_repo_url_as_configured_in_runbot parts/$repo_name $commit_hash branch=$current_branchname

Known issues / Roadmap

• none currently

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Credits

Maintainer

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit https://odoo-community.org.