Continuous Integration Larry Cai  [email_address]
Profile Larry , an open source, collaboration & Agile evangelist Software Practice Pioneer  to discover the best suitable methods and tools to improve the efficiency of software development @larrycaiyu [email_address]
Agenda Tools Continuous Integration Overview Deployment Continuous Delivery (Next step)
Continuous integration Continuous Integration is a software development practice where members of a team  integrate their work frequently , usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an  automated build (including test)  to detect integration errors as quickly as possible .  Basic automation in CI Compile, Unit level testing (code) Acceptance Testing (verification) Feedback to develop team Ref:  http:// martinfowler.com/articles/continuousIntegration.html
CI overview Source:  http://www.javaworld.com/javaworld/jw-12-2008/images/CIOverview.jpg
Agenda Tools Continuous Integration Overview Deployment Continuous Delivery (Next step)
CI server - Hudson vs. Jenkins Hudson is a de-facto CI standard used for lots of products Easy to start, configure and extending (300+ plugins) Easy to handle your legacy system Hudson 1.394  (sun + community) Hudson (oracle) Jenkins (community) Since 2011
Public TV Source: Extreme feedback  http://wiki.hudson-ci.org/display/HUDSON/eXtreme+Feedback+Panel+Plugin or Radiator View Plugin  http://wiki.hudson-ci.org/display/HUDSON/Radiator+View+Plugin
sonar
Nexus – java 3pp management Maven repository manager acts as a proxy/cache between you and the internet Nexus is one of the popular tools (others are Artifactory, Archiva)
Agenda Tools Continuous Integration Overview Deployment Continuous Delivery (Next step)
deployment YOUR PROBLEM ?
Some tips Start now from what you have Dedicated people (not resource) for 1-2 years Decrease build time (machine first) Transparency, Visible Automate everything after code is checked-in Step by step (could put goal to the team)  Continuous improvement
Agenda Tools Continuous Integration Overview Deployment Continuous Delivery (Next step)
Continuous delivery http://q.weibo.com/475225

Continuous Integration Introduction

  • 1.
    Continuous Integration LarryCai [email_address]
  • 2.
    Profile Larry ,an open source, collaboration & Agile evangelist Software Practice Pioneer to discover the best suitable methods and tools to improve the efficiency of software development @larrycaiyu [email_address]
  • 3.
    Agenda Tools ContinuousIntegration Overview Deployment Continuous Delivery (Next step)
  • 4.
    Continuous integration ContinuousIntegration is a software development practice where members of a team integrate their work frequently , usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible . Basic automation in CI Compile, Unit level testing (code) Acceptance Testing (verification) Feedback to develop team Ref: http:// martinfowler.com/articles/continuousIntegration.html
  • 5.
    CI overview Source: http://www.javaworld.com/javaworld/jw-12-2008/images/CIOverview.jpg
  • 6.
    Agenda Tools ContinuousIntegration Overview Deployment Continuous Delivery (Next step)
  • 7.
    CI server -Hudson vs. Jenkins Hudson is a de-facto CI standard used for lots of products Easy to start, configure and extending (300+ plugins) Easy to handle your legacy system Hudson 1.394 (sun + community) Hudson (oracle) Jenkins (community) Since 2011
  • 8.
    Public TV Source:Extreme feedback http://wiki.hudson-ci.org/display/HUDSON/eXtreme+Feedback+Panel+Plugin or Radiator View Plugin  http://wiki.hudson-ci.org/display/HUDSON/Radiator+View+Plugin
  • 9.
  • 10.
    Nexus – java3pp management Maven repository manager acts as a proxy/cache between you and the internet Nexus is one of the popular tools (others are Artifactory, Archiva)
  • 11.
    Agenda Tools ContinuousIntegration Overview Deployment Continuous Delivery (Next step)
  • 12.
  • 13.
    Some tips Startnow from what you have Dedicated people (not resource) for 1-2 years Decrease build time (machine first) Transparency, Visible Automate everything after code is checked-in Step by step (could put goal to the team) Continuous improvement
  • 14.
    Agenda Tools ContinuousIntegration Overview Deployment Continuous Delivery (Next step)
  • 15.

Editor's Notes

  • #3 Peter: Maybe some short sentence on experience. “I have been developing software for xx years”.