The document discusses continuous delivery in software development, defining it as a discipline that allows for the seamless release of software to production. It outlines the evolution of a team's deployment process, detailing iterations of automation and various challenges encountered along the way. The document concludes with recommendations for best practices and resources for implementing continuous delivery using tools like Jenkins and Maven.

1. Continuous
Delivery
in Java
Cose che abbiamo imparato
facendoci del male
Codemotion Milano ‘15

2. @pdincau
Here We Are
@pierodibello

3. Continuous Delivery?
What is

4. “Continuous Delivery is a software development discipline where you
build software in such a way that the software can be released to
production at any time.”
Martin Fowler*
* martinfowler.com/bliki/ContinuousDelivery.html

5. “Continuous Delivery is nothing more than reducing the
stress you get when you deliver business value to the customer ”
My Team*
* Come and ask!

6. n t
Continuous Delivery...
What is

7. Continuous Integration

8. Continuous Deployment

9. “Safety” Deploy rules

11. Technically
Speaking

12. Deploy any specific working version to
production with confidence

13. 3 ways

14. Rodeo Style

15. No tests
Manual deploy
Snowflake environments
Non predictable outcome
Few or very little collaboration

16. Rodeo Style

17. By the book

18. Fast Feedback
Done is released
Shared responsibility
Everything is automated
Repeatable and reliable process

19. Start small and iterate

20. Once upon
a time...

21. We did know...

22. Previous deployment process was painful
Database continuously change
Different environments

23. Iterationn.1
No
Automation

24. Environment replica on AWS
Manual build
Manual DB migrations
Deploy with scp to remote JBoss

25. It was our
own choice...

26. ...but we felt like this

27. No automation at all
When was our last deploy?

28. A taste of
Automation
Iterationn.2

29. Set up a basic Jenkins installation
Test and build triggered on push
DB migration using Liquibase
Task to deploy on AWS

30. This worked for a while

31. Errors in MyBatis DB mappers
Wrong/Missing wirings

32. Meanwhile...

33. Yay! Environments are ready!

34. Deploy
Everywhere
Iterationn.3

35. New Jenkins job to run integration tests
Track slowest tests
First official deploy an all environments

36. …with different DB drivers !#$?!

37. Duplication

38. Incorrect use of mvn profiles
N-builds for N-environments
Long build and deploy time

39. Single
Artefact
Iterationn.4

40. Got rid of configurations using JBoss
*Unique* artefact for all environments
Deploy version X.Y.Z from Nexus

41. We started getting fast

42. But QA were not so happy
Branches, branches everywhere!

43. Make
them happy
Iterationn.5

44. An environment for QA
Tags over branches
Track deployed version

45. Devs love QAs

46. Acceptance tests

47. Explained values and
motivations to Product Owner

48. Self-service deploy

49. Remove Candidate
Clean Up
Clean Up
Build it...
Migrate
!
Database
Fetch
Unit Tests
Build
Build
Integration Test
!
Integration
Deploy
Publish
UAT
QA and Publish

50. Frontend Angular
!
Web
...and deliver it
Deploy ESB
!
ESB
Deploy staging
!
Deploy Staging
Deploy API
Deploy Core
Backend
Migrate
!
Database

51. Things we are
experimenting

52. Parallelization
Environments Provisioning
Jenkins under git
Squash migrations to snapshot

53. What we would do
differently...

54. Pipeline with “placeholders”
Extract configurations asap
Explain at the beginning the values behind

55. Things we will keep
doing...

56. Build the pipeline iteratively
Share pipeline responsibility
Use the tool that best fit your needs

57. Recommended reading

58. Take a look at these
Real-World Strategies for Continuous Delivery
with Maven and Jenkins
https://www.youtube.com/watch?v=McTZtyb9M38
Visualizations of Continuous Delivery
http://continuousdelivery.com/2014/02/visualizations-of-continuous-delivery/

63. That’s all!

64. @pdincau@pierodibello

65. https://creativecommons.org/licenses/by-nc-sa/3.0/
Thanks!