Continuous integration with Git & CI Joe

Simple Continuous Integration using Git and CI Joe
Shawn Price drupal.org: langworthy twitter: @sprice

Continuous Integration Defined
"Continuous Integration is a software development practice where members of a team integrate their work frequently..." "Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly" - Martin Fowler
martinfowler.com/articles/continuousIntegration.html

Continuous Integration Defined
Continuous Integration is a fancy term for “run your project’s tests after someone pushes to the repository and notify interested parties if they fail” - Chris Wanstrath
github.com/blog/471-continuous-integration-spring-cleaning

Components of Continuous Integration
Use a code repository
Test your code
Automate the testing

In the beginning there was FTP.

In the beginning there was FTP. And things were good.

5 minutes later....

5 minutes later.... Things were bad.

5 minutes later.... Things were bad. "Who made that change?" "There's a bug, lets put the previous version of the file back" etc.

Greetings Git!

Greetings Git! A free & open source distributed version control system.
git-scm.com/
progit.org/book/
drupal.org/community-initiatives/git

Using a code repository allows teams to:
track the history of changes
use branches to manage feature integration
efficiently deploy to production
efficiently roll-back changes

Meet the Amazing Module!

DEMO time:
Create a new git repository
Include Drupal and the Amazing module

Test your code

Test your code
Drupal 6: drupal.org/project/simpletest Simpletest is in Drupal 7 core.

Test your code
amazing.test
<?php
class AmazingTestCase extends DrupalWebTestCase { public static function getInfo () { return array ( 'name' => t( 'Amazing functionality' ), 'description' => ( 'Test for amazingness' ), 'group' => t( 'Amazing' ), ); } function setUp () { parent:: setUp ( 'amazing' ); } public function testAmazingPageContent () { $this -> drupalGet ( "amazing" ); $this -> assertResponse ( 200 ); $this -> assertText (t( 'Simply amazing!' )); } }

Test your code
DEMO time:
running tests in the Drupal UI
running tests with drush - github.com/yhahn/drush_test

Choosing a Continuous Integration server

Hudson?
Cruise Control?
and more...

Hudson? (Java)
Cruise Control? (Java)
and more... (many are tricky to install)

Meet CI Joe! github.com/defunkt/cijoe

CI Joe was created out of the desire to do CI simply
configure via git config
$ git config --add cijoe.runner "drush test MyTestCase"
use git hooks for notifications
easy to install with few dependencies (Ruby)
$ gem install cijoe
$ git clone git://github.com/you/yourrepo.git
$ cijoe yourrepo

CI Joe runs when it receives a POST

CI Joe runs when it receives a POST
$ curl -d "payload" http://ci.example.com:4567

Notifications are sent via git hooks

.git/hooks/build-worked
#!/bin/bash
EMAIL="me@example.com"
/usr/sbin/sendmail "$EMAIL" <<EOD
To: $EMAIL
Subject: Your tests passed
From: Testbot <testbot@ci.example.com>
The latest integrations are good. The tests passed.
EOD

.git/hooks/build-failed
#!/bin/bash
EMAIL="me@example.com"
/usr/sbin/sendmail "$EMAIL" <<EOD
To: $EMAIL
Subject: Your tests failed
From: Testbot <testbot@ci.example.com>
The latest integrations are bad. The tests failed. Better luck next time.
EOD

Bringing it all together
push changes to remote git repository

Post-Receive URL triggers a POST to CI Joe

CI Joe runs tests

CI Joe runs tests
CI Joe sends notification via git hook

DEMO TIME!

Questions?

Thank You.

Continuous integration with Git & CI Joe

by Shawn Price

Accessibility

Categories

Upload Details

Usage Rights

Statistics