• Save
Continuous Integration System
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Continuous Integration System

  • 5,632 views
Uploaded on

Intro to Continuous Integration System

Intro to Continuous Integration System

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
5,632
On Slideshare
5,531
From Embeds
101
Number of Embeds
9

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 101

http://sccem.blogspot.com 32
http://zovtsit.vattenfall.se 30
http://zovtsit 14
http://www.slideshare.net 12
http://www.sccem.blogspot.com 5
http://aot-confluence.corp.vattenfall.com 4
http://sccem.blogspot.dk 2
http://sccem.blogspot.pt 1
http://sccem.blogspot.sg 1

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 & Hudson
  • 2. Agenda
    • Objective
    • What is Continuous Integration (CI)?
    • Why do we need Continuous Integration (CI)?
    • Typical CI Architecture
    • Advantages of CI
    • CI Requirements
    • What is Hudson?
    • Why Hudson?
  • 3. Objective
    • Basic Introduction to Continuous Integration System & Hudson
  • 4. What is Continuous Integration (CI)?
    • Continuous Integration is the process of assembling software
    • everytime code changes. CI Helps to “ Integrate Early,
    • Integrate Often ” reducing the lifespan of a defect.
    • CI is seen as a CenterPiece for Quality, as it ensures the health of the
    • software through running a build with every change delivered to the
    • SCM System.
  • 5. Why Continuous Integration (CI)?
    • Replace Big (and long) Integration phases into small and frequent ones
    • Minimize Integration Efforts
    • Helps to produce CRISP ( Complete, Repeatable, Informative, Schedulable, Portable) Builds.
    • Reduces repetitive manual processes (Move towards Automation)
    • Generate Deployment package at any time and at any place
    • Establish greater confidence with the development teams
    • Centralization
    • etc
  • 6. Typical CI Architecture SCM Repo/DB CI Server Tester Test Server Deliver Changes Poll Schedule Bugs Dev Team Release Package Automated Deployment Regular Testing Reports DB Generate Send DB Updates Send Feedback E-Mail Produce Software Compile J U nit Run Text Message
  • 7. Advantages of Continuous Integration (CI)
    • Smoother Integration
    • Automated Build, Release, Deploy, Testing Cycle
    • Regular Stable Releases
    • Faster and Easier Bug-Fixing
    • Better Visibility & More Confidence
    • Quick Feedback and Reporting
  • 8. Continuous Integration Requirements
    • A reliable build process using
      • ANT, Maven etc
    • An SCM System
      • Clearcase, Subversion etc
    • A Continuous Integration Server
      • Hudson, CruiseControl, Cruise, Meister etc
  • 9. What is Hudson?
    • Hudson is an Open-Source Continous Build Integration tool, which works with the SCM tools such as CVS, Subversion, Clearcase, PVCS etc and can build projects using Ant, Maven, Windows batch files or UNIX shell scripts .
  • 10. Why Hudson?
    • Web Based, Easy to Use
    • Lots of Plugins
    • Cool User Interface
    • ChangeSet Support
    • Easy to Setup, Configure and Administer
    • Powerful as it supports various SCM systems, build tools
    • Comprehensive Project Reporting & Dashboard
    • Security - Supports User Authentication and Restriction
    • Free and OpenSource – Zero Cost
    • Widely used in the industry
    • :
    • :
  • 11.
    • Thank You