A Pragmatic Approach to Continuous Delivery

Talk from jDays 2012

Transcript

1. A Pragmatic Approach to Continuous Delivery Ivar Grimstad jDays 2012 Ivar Grimstad 1
2. 2012-12-03 e.g. name of the presenter 2
3. @ivar_grimstad jDays 2012 Ivar Grimstad 3
4. • JUnit • Ant • Continuous Integration • Maven • Continuous Delivery A Little History jDays 2012 Ivar Grimstad 4
5. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Agile Manifesto jDays 2012 Ivar Grimstad 5 http://www.agilemanifesto.org/
6. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Principles behind the Agile Manifesto jDays 2012 Ivar Grimstad 6 http://www.agilemanifesto.org/
7. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Principles behind the Agile Manifesto jDays 2012 Ivar Grimstad 7 http://www.agilemanifesto.org/ Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount
8. A Pragmatic Approach to Continuous Delivery Motivation jDays 2012 Ivar Grimstad 8
9. • Build Binaries Once • One Process Deploy • Test Deployments • Flow • Fail -> Stop the Line The Deployment Pipeline jDays 2012 Ivar Grimstad 9
10. • Commit • Analysis • Deploy • Test • Deliver Remember that this is a pragmatic approach Deployment Pipeline Stages jDays 2012 Ivar Grimstad 10
11. • Compile • Test • Create binaries for later use The Commit Stage - Steps jDays 2012 Ivar Grimstad 11
12. The Commit Stage - Example jDays 2012 Ivar Grimstad 12
13. • Static Analysis The Analysis Stage - Steps jDays 2012 Ivar Grimstad 13
14. • Test Coverage • Duplications • Complexity • Coupling • Rule Compliance • Code Style The Analysis Stage - Metrics jDays 2012 Ivar Grimstad 14
15. Sonar jDays 2012 Ivar Grimstad 15
16. The Analysis Stage - Example jDays 2012 Ivar Grimstad 16
17. • Copy Artifact from Commit Stage • Deploy to Test Environment The Deploy Stage - Steps jDays 2012 Ivar Grimstad 17
18. The Deploy Stage - Example jDays 2012 Ivar Grimstad 18
19. • Choose a subset of tests to run • Run tests most likely to fail first The Test Stage - Steps jDays 2012 Ivar Grimstad 19
20. The Test Stage - Example jDays 2012 Ivar Grimstad 20
21. The Test Stage - Example jDays 2012 Ivar Grimstad 21
22. • Copy Artifact from Commit Stage • Deliver according to agreement The Deliver Stage - Steps jDays 2012 Ivar Grimstad 22
23. The Deliver Stage - Example jDays 2012 Ivar Grimstad 23
24. Jenkins Build Pipeline Plugin jDays 2012 Ivar Grimstad 24
25. Jenkins Build Pipeline Plugin jDays 2012 Ivar Grimstad 25
26. • Use Maven Release Plugin – mvn release:branch or mvn release:prepare – mvn release:perform • Jenkins Fingerprint Functionality What about Versioning? jDays 2012 Ivar Grimstad 26
27. Do not underestimate JavaDoc! What about Documentation? jDays 2012 Ivar Grimstad 27
28. • Blue/Green Deployments • Canary Releasing • Feature Toggles • Branch by Abstraction Designing for Continuous Delivery jDays 2012 Ivar Grimstad 28
29. • Manual Deployment • Deployment to production-like environment after development is complete • Manual configuration of production environment • Excessive Branching Antipatterns jDays 2012 Ivar Grimstad 29
30. • Every change should trigger the feedback process • Fast Feedback • Act on the Feedback To Sum Up jDays 2012 Ivar Grimstad 30
31. • Jenkins – Build Pipeline Plugin – Copy Artifact Plugin • Sonar • Maven – Maven Release Plugin – Maven Javadoc Plugin – Maven Glassfish Plugin (similar for all app servers) Tools jDays 2012 Ivar Grimstad 31
32. • Define your pipeline steps • Set up the jobs • Start configuring • Evolve your pipeline Where to start? jDays 2012 Ivar Grimstad 32
33. • Architecting for Continuous Delivery Axel Fontaine Tuesday 14:40 • Building a Continuous Deployment Pipeline with Maven Alan Parkinson Wednesday 13:30 More at jDays jDays 2012 Ivar Grimstad 33
34. It is not that hard! Remember… jDays 2012 Ivar Grimstad 34
35. You’re probably doing it already! …and jDays 2012 Ivar Grimstad 35
36. @ivar_grimstad http://www.agilejava.eu jDays 2012 Ivar Grimstad 36