The document presents a case study on continuous integration (CI), highlighting its importance in ensuring developers and quality assurance (QA) teams can effectively collaborate. It discusses the benefits of CI, such as reducing rework and enabling early identification of issues, and details various recommended practices and tools, including Hudson CI and others. The case study emphasizes the need for automated build and deployment processes, providing insights into configuration, execution, and tools available for different project needs.

1. Continuous Integration: A case study Vaibhav Kothari

2. Vaibhav Kothari Over 6 years of industry experience Quality Assurance – Lead, Talentica Software Quality Analyst, Infosys Education B Tech, IIT Delhi

3. Abstract Developer’s dilemma QA’s dilemma Continuous Integration ? Case study What is accomplished? Benefits of CI Recommended Practices Other Tools Available Q&A

4. Thought Exercise Goliath: Can you please get the build for client demo? David: OK…..oOPs! The build is failing!

5. Developer’s dilemma Will my changes integrate successfully with all versions of code? How much time/effort will it take to build and deploy from different source repository branches? Why can’t QA take this up?

6. QA’s dilemma How much time/effort it will take to build and deploy from different source repository branches? How much time/effort will it take to test builds from different sources? I can't build that often!

7. Continuous Integration?? As wiki says “ Continuous integration involves integrating early and often, so as to avoid the pitfalls of " integration hell ". The practice aims to reduce rework and thus reduce cost and time.”

8. Continuous Integration….

9. Continuous Integration…. Integrating the build process with continuous development. Concurrent build preparation from different branches. Integrating build system with deployment and test automation. Monitoring build and test.

10. CI in Agile development

11. Case Study Current Product development Lifecycle

12. Where does integration server stands ? Case Study

13. Features to look out for Basic Continuous Integration Build Triggering options Support for tools Set ups and usability Build logs and metrics Notifications Plugins, Extensions Case Study

14. Hudson CI Open source tool available as deployable war file. Each build and deployment process can be set up as a separate project and run concurrently or subsequently. Supports distributed builds The most used CI server in an informal developer survey! Case Study

15. Case Study Tools to be Integrated Windows XP/Linux OS Selenium RC Test Automation Apache Tomcat 6.0 Web server Apache Ant Build Tool Subversion Version control Hudson CI Continuous Integration

16. Case Study: Setting up a Build Job…

17. Case Study: Defining Build Triggers…

18. Post build tasks Automate build and deployment process and server restart. Integrate Hudson with test automation suite Remote deployment of multiple builds and test suite invocation Case Study

19. Case Study: Post build tasks…

20. Distributed Builds Build distribution using Single Hudson installation. Single click using Master/Slave mode. Concurrency in largely distributed projects. Case Study

21. Case Study

22. Case Study…Slave set up in Hudson

23. Case Study….What’s achieved?

24. Nobody minds it! Single click process. Early identification of build issues. Early identification of bugs. Incremental development. Constant availability of sane build. Efficient use of Test Automation. More time for Quality improvement. Benefits of CI

25. Maintain a code repository Automate the build and Deployment Make your build self-testing Everyone commits every day Every commit (to mainline) should be built Keep the build fast Test in a clone of the production environment Everyone can see the results of the latest build Recommended Practices

26. Other Tools Available Tools Advantages Limitations Cruise Control - Supports wide project and SCM tool. - Good notification techniques - Large number of plugins - Complicated set up - XML based configuration Continuum - Easy to install and use - Web Administrative console - Not suitable for big projects Luntbuild - Easy to install and use - Web Administrative console - Supports wide range of tools - Not support remote project build up TeamCity - Supports distributed build - Professional support (JetBrains) - Advanced options Commercial tool (free for 10 projects) Bamboo Advanced distributed build options Integrates with JIRA Commercial tools

27. Q&A