Travis CI Integration¶
Review Board can integrate with Travis CI to do test builds of code changes and report the results back as a status update on the review request.
To configure integration with Travis CI, click Add a new configuration on the Integrations page in the Administration UI. You can create multiple configurations of the integration to do builds for each repository which supports Travis CI builds.
The Name field can be used to set a name for this particular configuration. This allows you to keep track of which is which in the case where you have multiple Travis CI configurations.
If at any point you want to stop triggering builds but do not want to delete the configuration, you can uncheck Enable this integration.
Conditions allows you to set conditions for when Review Board will trigger a build. At a minimum, you should set a condition to match a specific repository. Even if you only have one repository configured now, you’ll want to set this up so things don’t break if you connect a second one. If needed, you can create complex rules for which review requests get matched with this config (for example, if you only want to run a test suite for certain branches).
The Build Config allows you to specify a replacement for the
.travis.yml file. This should define the build for your
project in isolation, removing any deployment or notification steps. The
required steps for building the patch and reporting results back to Review
Board will be automatically included when the build is triggered.
This configuration should not include any secrets, since code submitted through Review Board will have access to the decrypted data (and these secrets are not needed when there is no deployment or notification).
language: python python: 2.7 install: - python setup.py develop - pip install -r dev-requirements.txt script: - python ./tests/runtests.py
There’s one additional optional field, Build Branch. By default,
the Travis CI user interface will show all builds as occurring on
This field allows you to override the branch name to be something else, as to
separate review request builds from regular builds.
We recommend creating and pushing a dummy branch named “review-requests” to your repository, and then filling in that name here. The actual contents of that branch are unimportant, and it never needs to be updated, since the source will be completely replaced during the build process.