Continuous Integration: A Case Study

Uploaded on

Session Presented at 2nd Conference On Software Quality held on 25-26 March 2011 in Pune, India …

Session Presented at 2nd Conference On Software Quality held on 25-26 March 2011 in Pune, India

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Continuous Integration: A case study Vaibhav Kothari Talentica Software (I) Pvt ltd
  • 2. Abstract
      • Developer’s dilemma
      • QA’s dilemma
      • Continuous Integration ?
      • Case study
      • What is accomplished ?
      • Benefits of CI
      • Recommended Practices
      • Other Tools Available
      • Q&A
  • 3. Developer’s dilemma
      • Will my changes integrate successfully with all versions of code?
      • How much time/effort it will take to build and deploy from different source repository branches?
      • Why can’t QA take this up!!
  • 4. 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 test builds from different sources?
      • I can't build that often!
  • 5. 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.”
  • 6. Continuous Integration….
  • 7. 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.
  • 8. CI in agile development
  • 9. Case Study
      • Current Product development Lifecycle
  • 10. Case Study
      • Where does integration server stands ?
  • 11.
    • 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
  • 12.
    • 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
  • 13. Case Study
      • Tools to be Integrated
    Windows XP/Linux OS Selenium RC Test Automation Apache Tomcat 6.0 Web server Apache Ant Build Tool Sub version Version control Hudson CI Continuous Integration
  • 14. Case Study… Setting up a build Job
  • 15. Case Study….. Defining build triggers
  • 16.
    • 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
  • 17. Case Study… Post build tasks
  • 18.
    • Distributed Builds
      • Build distribution using Single Hudson installation.
      • Single click using Master/Slave mode.
      • Concurrency in largely distributed projects.
    Case Study
  • 19. Case Study… Building Remotely
  • 20. Case Study… Slave set up in Hudson
  • 21. Case Study…. What’s achieved?
  • 22.
      • 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
  • 23.
      • 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
      • Make it easy to get the latest deliverables
      • Everyone can see the results of the latest build
    Recommended Practices
  • 24. 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)
      • Advanced distributed build options
      • Integrates with JIRA
      • Commercial tools
  • 25. Q&A