This document summarizes the key components of setting up simple continuous integration for a Drupal project using Git and CI Joe. It discusses using a code repository like Git to track changes, writing automated tests for the code using Drupal's Simpletest framework, and using the CI server CI Joe to run the tests on each push and notify developers of the results via email. The document provides examples of writing a test class and setting up CI Joe and git hooks to integrate all the pieces for continuous integration.

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

2. 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

3. 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

4. Components of Continuous Integration Use a code repository

5. Test your code

6. Automate the testing

7. Use a code repository

8. Use a code repository In the beginning there was FTP.

9. Use a code repository In the beginning there was FTP. And things were good.

10. Use a code repository 5 minutes later....

11. Use a code repository 5 minutes later.... Things were bad.

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

13. Use a code repository Greetings Git!

14. Use a code repository Greetings Git! A free & open source distributed version control system. git-scm.com/

15. progit.org/book/

16. drupal.org/community-initiatives/git

17. Use a code repository Using a code repository allows teams to: track the history of changes

18. use branches to manage feature integration

19. efficiently deploy to production

20. efficiently roll-back changes

21. Use a code repository Meet the Amazing Module!

22. Use a code repository DEMO time: Create a new git repository

23. Include Drupal and the Amazing module

24. Test your code

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

26. 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 ( &quot;amazing&quot; ); $this -> assertResponse ( 200 ); $this -> assertText (t( 'Simply amazing!' )); } }

27. Test your code DEMO time: running tests in the Drupal UI

28. running tests with drush - github.com/yhahn/drush_test

29. Automate the testing

30. Automate the testing Choosing a Continuous Integration server

31. Automate the testing Choosing a Continuous Integration server Hudson?

32. Cruise Control?

33. and more...

34. Automate the testing Choosing a Continuous Integration server Hudson? (Java)

35. Cruise Control? (Java)

36. and more... (many are tricky to install)

37. Automate the testing Meet CI Joe! github.com/defunkt/cijoe