Name: ci-sample
Owner: Rainforest QA
Description: Example web application with Rainforest configured for multiple CI systems
Created: 2015-02-04 00:14:06.0
Updated: 2018-03-08 15:53:47.0
Pushed: 2015-02-09 23:09:08.0
Homepage: null
Size: 247
Language: Shell
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
The goal of this repository is to show how to configure various CI servers to work with Rainforest.
This repository assums the following workflow. All developers would start new work from the develop branch. They would create a new feature branch for each shippable piece of code.
When they are ready, they would merge that feature branch in the develop branch using a pull request or the git command line tool.
After the develop branch is updated, the CI server would notice the change and start a new build. The build would run the unit tests, deploy the code to a staging environment (hosted in Heroku in our example) and trigger a Rainforest run against that environment.
Once the Rainforest run is successful, the CI server will merge back the code in the master branch. This will in turn kick off another CI build of that branch. The master branch is in turned deploy to production.
This is our recommended way of deploying code if your Rainforest test suite is comprehensive enough. This flow can easily be adapted to fit your needs.