DevConTLV 2013 - import continuous.delivery.*

Continuous delivery pipeline with Jenkins, Artifactory and LiveRebel

Transcript

1. import continuous.delivery.* Anton Arhipov @antonarhipov Product Lead ZeroTurnaround Tuesday, February 19, 13
2. Tuesday, February 19, 13
3. Before CD Developer Release Engineer SysOp QA Tuesday, February 19, 13
4. Powered by CD Developer CD Engineer SysOp QA Manager Tuesday, February 19, 13
5. Fedex process • Package • Dropoff • Transfer • Delivery • Profit! Tuesday, February 19, 13
6. • Package • Test • Approve • Deploy • Profit! Java EE Tuesday, February 19, 13
7. • 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? Tuesday, February 19, 13
8. Fedex FAIL Tuesday, February 19, 13
9. Software FAIL Tuesday, February 19, 13
10. Tuesday, February 19, 13
11. Continuous Delivery Pipeline Tuesday, February 19, 13
12. A pipeline? Source: http://startupblog.files.wordpress.com/2008/09/pipeline1.jpg Tuesday, February 19, 13
13. Continuous Delivery pipeline! Source: http://www.flickr.com/photos/mikeleishman/1787764289/ Tuesday, February 19, 13
14. • Orchestration Platform • Delivery Manager • Artifact Repository The Pipeline Let’s talk about tools! Tuesday, February 19, 13
15. Jenkins (OSS Continuous Integration Server) Tuesday, February 19, 13
16. Orchestration platform Tuesday, February 19, 13
17. LiveRebel (Commercial Delivery Manager) Tuesday, February 19, 13
18. • Deploy/Undeploy • Update • No downtime • No lost sessions • Plain old restarts • Environment/deployment status What can you do with LiveRebel? Tuesday, February 19, 13
19. And we freakin’ built it! Tuesday, February 19, 13
20. Artifactory (Binary Repository) Tuesday, February 19, 13
21. Tuesday, February 19, 13
22. The Pipeline / The Repos Tuesday, February 19, 13
23. Test Build Repository Pipeline Build Test QA QA Dist Deployment Test RC GO! Prod Staging Tuesday, February 19, 13
24. Pipeline phases Tuesday, February 19, 13
25. Build phase Tuesday, February 19, 13
26. Test phase Tuesday, February 19, 13
27. QA phase Tuesday, February 19, 13
28. Production phase Tuesday, February 19, 13
29. Dirty details in Jenkins Tuesday, February 19, 13
30. Pipeline view in Jenkins Tuesday, February 19, 13
31. Step configuration in Jenkins Tuesday, February 19, 13
32. curl -X POST -H "Content-Type: application/ vnd.org.jfrog.artifactory.build.PromotionRequest+json" -d {"status": "in qa", "comment" : "Promoted to QA", "ciUser": "jenkins", "targetRepo" : "qa"} http://host:8081/artifactory/api/build/promote/app/${BLD} Artifact promotion in with REST API Tuesday, February 19, 13
33. Package status information Tuesday, February 19, 13
34. /LYH5HEHO&RPPDQG&HQWHU 3OD\ $SSOLFDWLRQVHUYHU $SSOLFDWLRQVHUYHU /LYH5HEHOGDHPRQ /LYH5HEHOGDHPRQ /LYH5HEHODJHQW /LYH5HEHODJHQW +773 +773 KHUHEHLQWHUQHWV *8, &/, 5(67$3, + +773 &,SOXJLQV Here be internetz! Deployment Tuesday, February 19, 13
35. • Database • Configuration & Environment • Tests & Monitoring • Rollback Themes Not Covered Tuesday, February 19, 13
36. • 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? Tuesday, February 19, 13
37. The answers are in the pipeline! Tuesday, February 19, 13
38. • 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 Tuesday, February 19, 13
39. What’s changed? Tuesday, February 19, 13
40. What’s changed? • Increased significance of automated QA Tuesday, February 19, 13
41. What’s changed? • Increased significance of automated QA • Reduced manual testing Tuesday, February 19, 13
42. What’s changed? • Increased significance of automated QA • Reduced manual testing • Infrastructure roles NOT involved with release Tuesday, February 19, 13
43. What’s changed? • Increased significance of automated QA • Reduced manual testing • Infrastructure roles NOT involved with release • Release approval is a business decision Tuesday, February 19, 13
44. 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 Sounds simple, eh? Tuesday, February 19, 13
45. Q & A @antonarhipov anton@zeroturnaround.com Tuesday, February 19, 13