Organizing continuous delivery pipeline with Jenkins, Artifactory & LiveRebel

1. import continuous.delivery.*
Anton Arhipov
@antonarhipov
Product Lead
ZeroTurnaround
Monday, November 19, 12

2. Agenda
Agile Manifesto says:
INDIVIDUALS and INTERACTIONS
over
PROCESSES and TOOLS,
blah, blah, blah ...
Monday, November 19, 12

3. Agenda
PROCESSES and TOOLS
Monday, November 19, 12

4. Fedex process
• Package
• Dropoff
• Transfer
• Delivery
• Profit!
Monday, November 19, 12

5. Java EE
• Package
• Test
• Approve
• Deploy
• Profit!
Monday, November 19, 12

6. Questions?
• 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?
Monday, November 19, 12

7. Fedex FAIL
Monday, November 19, 12

8. Software FAIL
Monday, November 19, 12

9. Monday, November 19, 12

10. Continuous Delivery
Pipeline
Monday, November 19, 12

11. A pipeline?
Source: http://startupblog.files.wordpress.com/2008/09/pipeline1.jpg
Monday, November 19, 12

12. Continuous Delivery pipeline!
Source: http://studentthinktank.eu/wp-content/uploads/2012/02/03_TURKMEN-PIPELINE.jpg
Monday, November 19, 12

13. Philosophy
• Automate
• Record
• Test
• Recover
Monday, November 19, 12

14. The Pipeline
• Orchestration Platform
• Delivery Manager
• Artifact Repository
Monday, November 19, 12

15. Jenkins
(OSS Continuous Integration Server)
Monday, November 19, 12

16. Orchestration
platform
Monday, November 19, 12

17. LiveRebel
(Commercial Delivery Manager)
Monday, November 19, 12

18. What can you do with LiveRebel?
• Deploy/Undeploy
• Update
• No downtime
• No lost sessions
• Plain old restarts
• Environment/deployment status
Monday, November 19, 12

19. Why LiveRebel?
• No good OSS alternative
• Supports many app servers
• No downtime updates
• Integrates with OSS projects
Monday, November 19, 12

20. And we freakin’
built it!
Monday, November 19, 12

21. Artifactory
(OSS/Commercial Artifact Repository)
Monday, November 19, 12

22. Alternatives
• FTP
• Jenkins
• Nexus (and the like)
Monday, November 19, 12

23. Monday, November 19, 12

24. Now let’s build a
pipeline!
Monday, November 19, 12

25. The Pipeline / The Repos
Monday, November 19, 12

26. Repository Build Test QA RC
Pipeline Build Test QA Dist GO!
Deployment Test Staging Prod
Monday, November 19, 12

27. The tools in the pipeline
Monday, November 19, 12

28. Pipeline phases
Monday, November 19, 12

29. Build phase
Monday, November 19, 12

30. Test phase
Monday, November 19, 12

31. QA phase
Monday, November 19, 12

32. Production phase
Monday, November 19, 12

33. Dirty details in
Jenkins
Monday, November 19, 12

34. Themes Not Covered
• Database
• Configuration & Environment
• Tests & Monitoring
Monday, November 19, 12

35. Questions?
• 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?
Monday, November 19, 12

36. The answers are
in the pipeline!
Monday, November 19, 12

37. Pipeline Summary
• Jenkins jobs represent the workflow
• Artifactory is a sync-point
• LiveRebel manages apps and versions
• Manual flows with REST
• Tracking with scripts & text files
Monday, November 19, 12

38. Not bad, but what about the process??
Monday, November 19, 12

39. Monday, November 19, 12

40. Traditional Process
Developer QA
Release Engineer SysOp
Monday, November 19, 12

41. Powered by CD
QA
Developer Manager
CD Engineer SysOp
Monday, November 19, 12

42. What’s changed?
Monday, November 19, 12

43. What’s changed?
• Increased significance of automated QA
Monday, November 19, 12

44. What’s changed?
• Increased significance of automated QA
• Reduced manual testing
Monday, November 19, 12

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

46. 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

47. 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

48. Q&A
@antonarhipov
anton@zeroturnaround.com
Monday, November 19, 12