In the world of fast changing technologies and business requirements there is no way to stay with old-school approaches to develop software. Common, leave manual interaction behind, let machine do what it's best capable for and spend your time to solve real problems. During this talk I'm going to demonstrate how to build a sophisticated continuous development pipeline for Java based project to cover things like build, test, code quality, deploy and delivery using Gradle, Jenkins, SonarQube, Docker and Ansible. As an outcome of this presentation there will be an open source project with source code.

1. Continuous
Development
Pipeline

2. ● SA at EPAM Systems
● primary skill is Java
● hands-on-coding with Groovy, Ruby
● trying to learn some Erlang/Elixir
● passionate about agile, clean code and devops
Izzet Mustafayev@EPAM Systems
@webdizz webdizz izzetmustafaiev
http://webdizz.name

3. Agenda
● Introduction
● Step-by-step Implementation
■ Gradle
■ SonarQube
■ Jenkins
■ Ansible
● References
● Summary
● Q&A

4. Introduction

5. Continuous Integration

6. Principles
#1 Each change auto. built and deployed

7. Principles
#1 Each change auto. built and deployed
#2 Test on closed to prod environment

8. Principles
#1 Each change auto. built and deployed
#2 Test on closed to prod environment
#3 Integrate as frequently as possible

9. Principles
#1 Each change auto. built and deployed
#2 Test on closed to prod environment
#3 Integrate as frequently as possible
#4 The highest priority to fix failed build

10. Benefits
● Each change guarantees working code
● Each update should guarantee working
code ;)
● There is no delay for epic merge
● Less bugs - depends on your tests
efficiency*
● Allows to have code ready to go live

11. Challenges
● Need to build infrastructure
● Need to build team culture
● Need to support/enhance infrastructure
● Overhead with writing a lot of different
kind of tests

12. Continuous Delivery

13. Principles
#1 Every commit can result in a release

14. Principles
#1 Every commit can result in a release
#2 Automated tests are essential

15. Principles
#1 Every commit can result in a release
#2 Automated tests are essential
#3 Automate everything!

16. Principles
#1 Every commit can result in a release
#2 Automated tests are essential
#3 Automate everything!
#4 Done means released

17. Benefits
● Speed of delivery of business idea to
customer
● Easy going live deployment
● Less time spent on delivery - more profit
● More motivation to do more as you can
see what you can change/improve

18. Challenges
● Big effort to implement changes for:
○ database increment/rollback
○ infrastructure rollout/rollback
○ decrease down time …
● Need to get customers to buy in
● Security policies

19. Step-by-step
Implementation

20. Continuous
Development?

21. Gradle

22. 2.2.1

23. Gradle
- General purpose build system

24. Gradle
- General purpose build system
- Comes with a rich DSL based on Groovy

25. Gradle
- General purpose build system
- Comes with a rich DSL based on Groovy
- Follows ”build-by-convention” principles

26. Gradle
- General purpose build system
- Comes with a rich DSL based on Groovy
- Follows ”build-by-convention” principles
- Built-in plug-ins for JVM languages, etc

27. Gradle
- General purpose build system
- Comes with a rich DSL based on Groovy
- Follows ”build-by-convention” principles
- Built-in plug-ins for JVM languages, etc
- Declarative builds

28. Demo Time

29. Code
Quality

30. Ad-hoc,
fast
feedback

31. Ad-hoc,
fast
feedback
Over
time

32. SonarQube
- Measures code quality from day #0

33. SonarQube
- Measures code quality from day #0
- 7 axes of code quality

34. SonarQube
- Measures code quality from day #0
- 7 axes of code quality
- Helps to manage Technical Dept

35. SonarQube
- Measures code quality from day #0
- 7 axes of code quality
- Helps to manage Technical Dept
- Works not only for Java

36. SonarQube
- Measures code quality from day #0
- 7 axes of code quality
- Helps to manage Technical Dept
- Works not only for Java
- Good for dev, qa, archs & manager

37. Demo Time

38. Jenkins

39. Jenkins
- Distributed builds

40. Jenkins
- Distributed builds
- Plugin Support

41. Jenkins
- Distributed builds
- Plugin Support
- Easy installation, configuration

42. Jenkins
- Distributed builds
- Plugin Support
- Easy installation, configuration
- Strong community and eco-system

44. Notifications

45. Email sucks

46. Who cares?

47. During a day

48. End of day

49. Demo Time

50. Ansible

51. Ansible
- Agentless

52. Ansible
- Agentless
- SSH as a protocol, requires only Python

53. Ansible
- Agentless
- SSH as a protocol, requires only Python
- YAML based configuration

54. Ansible
- Agentless
- SSH as a protocol, requires only Python
- YAML based configuration
- Declarative and Decentralized

55. Ansible
- Agentless
- SSH as a protocol, requires only Python
- YAML based configuration
- Declarative and Decentralized
- Built-in security and encryption

56. Demo Time

57. Summary

58. Summary
● Culture is quite important

59. Summary
● Culture is quite important
● Automation is a thing

60. Summary
● Culture is quite important
● Automation is a thing
● Automated Testing is even more thing

61. Summary
● Culture is quite important
● Automation is a thing
● Automated Testing is even more thing
● Continuous process

62. References

63. ●
●
● http://www.gradle.org/books
● https://github.com/Netflix/gradle-template
● http://www.ansible.com/
● http://www.sonarqube.org/
● http://jenkins-ci.org/
● https://github.com/webdizz/bootiful-apps/
● https://github.com/webdizz/gradle-template
● https://github.com/eliogrin/CISEN/
References

64. Q&A

65. Izzet Mustafayev@EPAM Systems
@webdizz webdizz izzetmustafaiev
http://webdizz.name