-
Notifications
You must be signed in to change notification settings - Fork 2
Continuous Integration with Jenkins
For the TideSDK project, we use Jenkins for Continuous Integration. Currently the CI Hosting is being kindly provided and administered by one of the project developers and hosted at:
http://tidesdk.cloudapp.net:81/
Jenkins is an award-winning application that monitors the executions of repeated jobs. It's primary goal in our project is to build and execute our unit test on our software in conjunction with a plugin to git. The plugin listens for changes in our repository as the result of commits.
The automated continuous builds increase our productivity, and let us understand what is happening and who might be responsible. Jenkins provides a visual indication of good and bad builds. It is the responsibility of each developer to be diligent and notice when a build breaks or to respond to notices from Jenkins. Jenkins keeps those outputs and makes it easy for us to notice when something is wrong.
The following copyright and attribution applies to this document:
- Copyright © 2012 David Pratt (for TideSDK). All rights reserved.
CONTRIBUTORS:
- David Pratt