A snapshot
Continuous Integration Overview
Continuous integration is an agile software development practice which
facilitates in integrating the software changes frequently, stabilizes the product
though auto building & self-testing builds, and uses rapid feedback to solve the
integration issues fast. The goal of continuous integration is to produce a
working build as fast as possible.
Trigger
Check In
Notification
Stakeholders
Staging
Production
CI Server
RepositoryDevelopers
Why Continuous Integration?
 Insufficient testing
 Slow Release process
 Poor Project visibility
 Inflexible code base
 Issues detected late
 Automated testing
 Regular release
 Better visibility
 Healthy code base
 Issues detected early
CI = Continuous Integration
CI Best Practice
 Maintain a single source repository
 Build should be automated and self-testing
 Everyone in team commits everyday
 Fix the broken build immediately
 Everyone can see what’s happening
 Automated deployment
CI/DevOps Tools
Function Tools
Source code Management Git, Github, SVN, Perforce, TFS
Build Tools Ant, Maven, Gradle, MSBuild
Code Quality Analysis Sonar, Coverity, Fortify
Continuous Integration Jenkins, TFS, TeamCity, Bamboo, CruiseControl
Automated Testing Selenium, Jmeter , Cucumber
Configuration Management Puppet, Chef, Ansible
Continuous Deployment Tool uDeploy, Liquibase
Continuous Monitoring Nagios, Hygieia, Splunk
http://solutionframework.blogspot.in/

Continuous integration

  • 1.
  • 2.
    Continuous Integration Overview Continuousintegration is an agile software development practice which facilitates in integrating the software changes frequently, stabilizes the product though auto building & self-testing builds, and uses rapid feedback to solve the integration issues fast. The goal of continuous integration is to produce a working build as fast as possible. Trigger Check In Notification Stakeholders Staging Production CI Server RepositoryDevelopers
  • 3.
    Why Continuous Integration? Insufficient testing  Slow Release process  Poor Project visibility  Inflexible code base  Issues detected late  Automated testing  Regular release  Better visibility  Healthy code base  Issues detected early CI = Continuous Integration
  • 4.
    CI Best Practice Maintain a single source repository  Build should be automated and self-testing  Everyone in team commits everyday  Fix the broken build immediately  Everyone can see what’s happening  Automated deployment
  • 5.
    CI/DevOps Tools Function Tools Sourcecode Management Git, Github, SVN, Perforce, TFS Build Tools Ant, Maven, Gradle, MSBuild Code Quality Analysis Sonar, Coverity, Fortify Continuous Integration Jenkins, TFS, TeamCity, Bamboo, CruiseControl Automated Testing Selenium, Jmeter , Cucumber Configuration Management Puppet, Chef, Ansible Continuous Deployment Tool uDeploy, Liquibase Continuous Monitoring Nagios, Hygieia, Splunk
  • 6.