Continuous integration with Git & CI Joe
Download as ODP, PDF5 likes2,208 views
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.
Ad
More Related Content
What's hot (20)
Viewers also liked (8)
Ad
Similar to Continuous integration with Git & CI Joe (20)
![[English][Test Girls] Zero to Hero: Start Test automation with Cypress](https://cdn.slidesharecdn.com/ss_thumbnails/entestgirlstestingwithcypress-191024022807-thumbnail.jpg?width=560&fit=bounds)
Ad
Recently uploaded (20)
Continuous integration with Git & CI Joe
- 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
- 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/
- 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
- 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 ( "amazing" ); $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
- 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)
- 36. and more... (many are tricky to install)
- 37. Automate the testing Meet CI Joe! github.com/defunkt/cijoe
- 38. Automate the testing CI Joe was created out of the desire to do CI simply configure via git config
- 39. $ git config --add cijoe.runner "drush test MyTestCase"
- 40. use git hooks for notifications
- 41. easy to install with few dependencies (Ruby)
- 42. $ gem install cijoe
- 43. $ git clone git://github.com/you/yourrepo.git
- 44. $ cijoe yourrepo
- 45. Automate the testing CI Joe runs when it receives a POST
- 46. Automate the testing CI Joe runs when it receives a POST
- 47. $ curl -d "payload" http://ci.example.com:4567
- 48. Automate the testing Notifications are sent via git hooks
- 49. Automate the testing Notifications are sent via git hooks .git/hooks/build-worked #!/bin/bash
- 52. To: $EMAIL
- 53. Subject: Your tests passed
- 55. The latest integrations are good. The tests passed.
- 56. EOD
- 57. Automate the testing Notifications are sent via git hooks .git/hooks/build-failed #!/bin/bash
- 60. To: $EMAIL
- 61. Subject: Your tests failed
- 63. The latest integrations are bad. The tests failed. Better luck next time.
- 64. EOD
- 65. Bringing it all together push changes to remote git repository
- 66. Bringing it all together push changes to remote git repository
- 67. Post-Receive URL triggers a POST to CI Joe
- 68. Bringing it all together push changes to remote git repository
- 69. Post-Receive URL triggers a POST to CI Joe
- 70. CI Joe runs tests
- 71. Bringing it all together push changes to remote git repository
- 72. Post-Receive URL triggers a POST to CI Joe
- 73. CI Joe runs tests
- 74. CI Joe sends notification via git hook
- 75. Bringing it all together DEMO TIME!
- 76. Questions?
- 77. Thank You.