Upgrade to Pro — share decks privately, control downloads, hide ads and more …

import continuous.delivery.*

Anton Arhipov
November 17, 2012

import continuous.delivery.*

Organizing continuous delivery pipeline with Jenkins, Artifactory & LiveRebel

Anton Arhipov

November 17, 2012
Tweet

More Decks by Anton Arhipov

Other Decks in Technology

Transcript

  1. INDIVIDUALS and INTERACTIONS over Agenda PROCESSES and TOOLS, blah, blah,

    blah ... Agile Manifesto says: Monday, November 19, 12
  2. • What exactly is in prod now? • How did

    it get deployed? • How did it get there? • Where did it come from? • How did you package the application? Questions? Monday, November 19, 12
  3. • Deploy/Undeploy • Update • No downtime • No lost

    sessions • Plain old restarts • Environment/deployment status What can you do with LiveRebel? Monday, November 19, 12
  4. • No good OSS alternative • Supports many app servers

    • No downtime updates • Integrates with OSS projects Why LiveRebel? Monday, November 19, 12
  5. Test Build Repository Pipeline Build Test QA QA Dist Deployment

    Test RC GO! Prod Staging Monday, November 19, 12
  6. • Database • Configuration & Environment • Tests & Monitoring

    Themes Not Covered Monday, November 19, 12
  7. • How do you package the application? • Where did

    it come from? • Where does it go? • How does it get deployed? • What exactly is in prod now? Questions? Monday, November 19, 12
  8. • Jenkins jobs represent the workflow • Artifactory is a

    sync-point • LiveRebel manages apps and versions • Manual flows with REST • Tracking with scripts & text files Pipeline Summary Monday, November 19, 12
  9. What’s changed? • Increased significance of automated QA • Reduced

    manual testing • Infrastructure roles NOT involved with release Monday, November 19, 12
  10. What’s changed? • Increased significance of automated QA • Reduced

    manual testing • Infrastructure roles NOT involved with release • Release approval is a business decision Monday, November 19, 12
  11. What’s changed? • Increased significance of automated QA • Reduced

    manual testing • Infrastructure roles NOT involved with release • Release approval is a business decision • Automation is the key Too good to be true, eh? Monday, November 19, 12