• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Continous Delivery with CQ

Continous Delivery with CQ



Presentation “Continous Delivery with CQ“ by Oliver Burkhalter at CQCON2013 in Basel on 19 and 20 June 2013.

Presentation “Continous Delivery with CQ“ by Oliver Burkhalter at CQCON2013 in Basel on 19 and 20 June 2013.



Total Views
Views on SlideShare
Embed Views



1 Embed 1

http://www.markszulc.com 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Continous Delivery with CQ Continous Delivery with CQ Presentation Transcript

    • Continuous Delivery with CQThe way of automating the Software Development processOliver BurkhalterBasel, 20. Juni 2013
    • © Unic - Seite 2Agenda• About me• Continuous Integration(CI) and Continuous Delivery(CD)• CQ and CI/CD implementation example• Demo
    • © Unic - Seite 3• Oliver Burkhalter (age = 28)• Since 2007 at Unic AG• Likes: Software Development, People/Teams, Baking, Thun CityAbout me
    • © Unic - Seite 4One-ClickReleasesDeploymentsProduction
    • © Unic - Seite 5What is CI and CD?ContinuousIntegrationContinuousDeliveryContinuousDeploymentNon-Production environment Production environment
    • © Unic - Seite 6• Continuous Integration:• Team members integrate their work daily• All the components are automatically integrated and tested by the CI systemWhat is CI and CD?
    • © Unic - Seite 7• Continuous Delivery:• Is the advancement of CI• Is an end-to-end approach (from dev to end user)• Software is always in a production-ready state• It is the technique to automate thebuild, test and deployment process• Fail Fast pattern• Pipeline Pattern from Jez Humble&Co.What is CI and CD?
    • © Unic - Seite 8• Continuous Deployment:• Continuously deployment to the Production environment (one-click idea)• From Development to Production• “Extreme Cont. Delivery”What is CI and CD?Deployment
    • © Unic - Seite 9Why
    • © Unic - Seite 10
    • © Unic - Seite 11• Forces us to write Quality software• The overall Thinking changes fromdev -> test system to dev -> end user system• Faster release cycles are possible• Automated Software Development Process is less error prone• Team Ownership of the release process (not only «Release Manager»,infrastructure is also code)• Everybody can do a release (one click)Why?
    • © Unic - Seite 12Implementation example stackWriteBuildTestDeployRunApache MavenJenkinsJUnitHtmlUnitJenkinsAntJenkins
    • © Unic - Seite 13• With Maven Plugins: Auto start/stop of CQ, deployment of CQ packages over theCRX HTTP interface• Running auto. tests with JUnit and HtmlUnit• Set of unit and integration tests• Automated Acceptance tests still in progressFoundation: CI
    • © Unic - Seite 14• Separate “delivery” and “infrastructure” Maven module• Delivery:• Deployment scripts• Infrastructure• Environment-specific configurations• Done with Ant scripts and custom Ant tasksNext: Continuous Delivery
    • © Unic - Seite 15• Direct deployment to the customers production environment• Example: Trusted Maven RepositoriesNext 2: Continuous Deployment
    • © Unic - Seite 16Demo
    • © Unic - Seite 17Click to edit Master title styleQuestions
    • © Unic - Seite 18Click to edit Master title styleThank you!
    • © Unic - Seite 19• http://martinfowler.com/articles/continuousIntegration.html• http://martinfowler.com/delivery.html• http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/References
    • © Unic - Seite 20