Distributed Test with CI

How Iora Health uses its CI server to offload all full runs of its test suite. Video of the presentation can be seen here http://bostonrb.org/presentations/teamcity-ci

Transcript

1. Distributed Test with CI How to keep heads down coding
2. Introduction • Will Mernagh • Work: Iora Health • Twitter: @im_a_muppet • Github: wmernagh
3. What I will cover • Our initial development process • The problem and why it had to change • Team City CI • Project Templates • Remote agents • Our current development process
4. Old dev process • Select the top story in our backlog. • Fetch the latest version of master. • Create a feature branch from master. • TDD the feature. • Get new tests to green. • Run the test suite and get all tests to green. • Create a pull request. • Upon acceptance merge into master and push to origin.
5. The Problem
6. Team City CI • http://www.jetbrains.com/teamcity/ • Java application. • Easy installation and setup. • Licensing fee for more than 3 agents. • On demand EC2 launch and termination.
7. Team City CI: Templates
8. Team City CI: Agents • Create an EC2 instance that can run your tests • Download the buildAgent.zip to instance and configure • Edit properties file • Boot at startup • Save it as an AMI
9. New Dev process • Select the top story in our backlog. • Fetch the latest version of master. • Create a feature branch from master. • TDD the feature. • Get new tests to green. • Run the test suite and get all tests to green. • Push to personal ci branch and wait for green before going to step 9. • Go to step 1. • Create a pull request. • Upon acceptance merge into master and push to origin.
10. Conclusion • Similar features are probably available on other CIs. • Cost of running multiple agents and licensing is less that developer time.
11. HEADS DOWN CODING