Your SlideShare is downloading. ×
Continous Integration: A Case Study
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Continous Integration: A Case Study

1,977

Published on

One of the challenges faced by many web development based projects is the integration of source code for multiple releases during parallel development. The task to build and test the multiple versions …

One of the challenges faced by many web development based projects is the integration of source code for multiple releases during parallel development. The task to build and test the multiple versions of source code can eat out the quality time and limit the efficiency of the development/QA team. The case study focuses to resolve the issues of extensive effort consumed in build and deployment process from multiple branches in source repository and aim at Identification of source code integration issues at the earliest stage. This can further be enhanced to limit the manual intervention by integration of build system with test automation tool.
The above can be achieved by using different CI tools (like Hudson/Bamboo/TeamCity/CruiseControl etc) for continuous build preparation and its integration with any test automation suite. The case study specifies the use of CI-Hudson tool for continuous integration using ANT tool for build preparation and further invoking the automation test suite developed using selenium. It also discusses the limitations and challenges of using such an integration system for testing a web based application deployed on Apache Tomcat server. It also details additional plugins available to enhance such an integration of multiple systems and what can be achieved using the above integration.

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,977
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
96
Comments
0
Likes
4
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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

×