Expertiza Continuous Integration: Difference between revisions
(Created page with "The build status for the Expertiza project is tracked by the http://about.travis-ci.org/blog/ Travis Continuous Integration tool. You can see the current status of the projec...") |
No edit summary |
||
| Line 2: | Line 2: | ||
You can see the current status of the project using the [[https://travis-ci.org/expertiza/expertiza Expertiza Travis Dashboard]] | You can see the current status of the project using the [[https://travis-ci.org/expertiza/expertiza Expertiza Travis Dashboard]] | ||
== Continuous Integration == | == Continuous Integration == | ||
Travis CI automatically builds the Expertiza project to make sure that no failures are introduced into the existing test suites after new code is committed. | |||
As of April 18th, 2013, the Travis CI configuration for Expertiza only builds and checks the cucumber test suite for failures on the master and production branches. | |||
== Benefits == | == Benefits == | ||
* Notifies the Expertiza Support List of test failures or changes in a build (previously failing tests passing after a build). | |||
* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]]. | |||
* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request. | |||
* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code | |||
* Allows Expertiza contributors to catch a build failure and roll back a commit. | |||
== Travis CI Build Configuration == | == Travis CI Build Configuration == | ||
The [[http://about.travis-ci.org/docs/user/build-configuration/ configuration documentation]] for Travis is very extensive but there are some things to note in regards to Expertiza. | |||
Configuration changes are done by modifying the .travis.yml configuration file in the root of the repository and committing to the master and/or production branch. | |||
Revision as of 19:44, 17 April 2013
The build status for the Expertiza project is tracked by the [Travis Continuous Integration] tool. You can see the current status of the project using the [Expertiza Travis Dashboard]
Continuous Integration
Travis CI automatically builds the Expertiza project to make sure that no failures are introduced into the existing test suites after new code is committed. As of April 18th, 2013, the Travis CI configuration for Expertiza only builds and checks the cucumber test suite for failures on the master and production branches.
Benefits
- Notifies the Expertiza Support List of test failures or changes in a build (previously failing tests passing after a build).
- Build status indicator on the Expertiza [Github readme].
- Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.
- Allows Expertiza contributors to determine whether a pull request is admissible before merging the code
- Allows Expertiza contributors to catch a build failure and roll back a commit.
Travis CI Build Configuration
The [configuration documentation] for Travis is very extensive but there are some things to note in regards to Expertiza. Configuration changes are done by modifying the .travis.yml configuration file in the root of the repository and committing to the master and/or production branch.