This document provides an overview of CI/CD with Jenkins. It defines continuous integration and continuous delivery, discusses the history and benefits of Jenkins, and covers Jenkins pipeline plugins. It also demonstrates how to build a basic pipeline in Jenkins and extend it by integrating Sonar code quality analysis prior to deployment.

1. Titel
Onderwerp
Verantwoordelijke afdeing, personen.
Datum
CI/CD with Jenkins
BlueOcean Pipelines
JTech / Juan Pablo de Castro
20/03/2019

2. 2
 Senior Java Developer (10+ years experience)
 Worked on a large scale of projects
- Frontend & Backend
 Current Client (De Nederlandse Bank DNB)
 Hobby’s
- Play Games, Watch Movies/Series, Walks, etc..
 Father of two
Introduction

3. 3
Overview & Objective
 Definition of CI/CD
 History of Jenkins
 Jenkins alternatives
 Jenkins Pipeline Plugins
 Build a mini Pipeline
 Extend the mini Pipeline

4. So what is Continuous
Integration (CI)?

5. 5
Continuous Integration

6. 6
Continuous Integration
Continuous Integration (CI) is a
development practice that requires
developers to integrate code into a shared
repository several times a day. Each
check-in is then verified by an automated
build, allowing teams to detect problems
early.

7. 7
What are the benefits?
 Reduce integration complexity
 Catch issues early
 Spend less time debugging
 Stop waiting to find out if your code’s going to work
Continuous Integration

8. 8
Practices
 Maintain a single source repository
 Automate the build
 Make your build self-testing
 Keep the build fast
 Everyone can see what’s happening
 Automate deployment
Continuous Integration

9. 9
How do we do it? / Scenario
 Dev: checkout source to local repository
 Dev: commit changes to remote repository
 CI: polling picks up changes
 CI: build, run unit- & integration tests
 CI: release & label software artifacts
 CI: informs team of successful release
 …
Continuous Integration

10. 10
How do we do it? / Scenario
 CI: if the build/test fails it notifies the team
 Dev: fixes the build & test as soon as possible
 Dev: commit & push changes to the repository
 CI: informs team on change/fix for broken build
 Team: continue integration ritual build & test
Continuous Integration

11. 11
Team responsibilities
 Team: check-in frequently
 Team: don’t commit broken or untested code
 Team: don’t check in when build is broken, fix first!
 Team: don’t check-in & leave the
building!
Continuous Integration

12. And what about Continuous
Delivery (CD)..?

13. 13
Continuous Delivery
Continuous Delivery (CD) is a development
practice where code changes are automatically
built, tested, and prepared for a release to
production.

14. But wait.. There’s another CD in
CI/CD?

15. 15
Continuous Deployment
Continuous Deployment (CD) is a software
development practice in which every code
change goes through the entire pipeline and is
put into production, automatically, resulting in
many production deployments every day.

16. 16
CI/CD/CD

17. History of Jenkins

18. 18
History of Jenkins
 2004 – Known as the Hudson project lead by Sun
Microsystems
 2005 – First release by Kohsuke Kawaguchi (founder)
 2010 – Oracle buys Sun Microsystems
 2011 – Oracle makes proposal to change the name of
Hudson to Jenkins

19. 19
Why Jenkins?
 Jenkins has plenty of configuration options
 Has a vibrant community of developers
 Large library of plugins
 Supports scripting languages like Groovy
 Integration with many build tools Maven, Gradle, Ant..
 Easy to install and free!
History of Jenkins

20. 20
History of Jenkins

21. Jenkins Alternatives

22. 22
Jenkins Alternatives

23. Jenkins Pipeline Plugins

24. 24
 Build Pipeline plugin
 Delivery plugin
 Jenkins Pipeline plugin (Pipeline as Code)
- Scripted Pipeline (Groovy as the foundation, Jekinsfile)
- Declarative Pipeline (Jenkinsfile)
 Blue Ocean Pipeline plugin
Jenkins Pipeline Plugins

25. 25
Build Pipeline plugin
Jenkins Pipeline Plugins

26. 26
Build Pipeline plugin
Jenkins Pipeline Plugins
 Requires configuration of separate build jobs
 Based on upstream/downstream jobs
 Job configuration needs to be stored

27. 27
Delivery plugin
Jenkins Pipeline Plugins

28. 28
Delivery plugin
Jenkins Pipeline Plugins
 Same requirements as Build Pipeline plugin
 Provides a different Pipeline visualization

29. 29
Jenkins Pipeline plugin
Jenkins Pipeline Plugins

30. 30
Jenkins Pipeline plugin
Jenkins Pipeline Plugins
 Based on Jenkinsfile
 Supports Pipeline as Code and offers syntax
flexibility (Scripted or Declarative)
 Scripted Syntax
- Power-users, very flexible, extensible, Groovy based
 Declarative Syntax
- Simple syntax (predefined structure)

31. 31
Jenkins Pipeline Plugins

32. 32
Jenkins Pipeline Plugins

33. 33
Jenkins Pipeline Plugins

34. 34
Why Jenkins Pipeline?
 Powerful set of automation tools
- Code: Pipeline can now be checked into source control
- Durable: Survives Jenkins master restarts
- Pausable: Stop and wait for user input or approval
- Versatile: Supports fork/join, loop and parallel scenarios
- Extensible: Supports extensions to DSL and integration with other
plugins
Jenkins Pipeline Plugins

35. 35
Blue Ocean plugin
Jenkins Pipeline Plugins

36. 36
Why Blue Ocean?
 New Project that rethinks the user experience
 Sophisticated visualization of CD Pipelines
 Pipeline Editor (UI as a guide)
 Personalization (Jenkins UI changes)
 Pinpoint precision (where did it go wrong?)
 Native integration for branches and pull requests
Jenkins Pipeline Plugins

37. Build a mini Pipeline

38. 38
Build a mini Pipeline

39. 39
Build a mini Pipeline

40. 40
 Head over to:
- https://jenkins.io/doc/tutorials/build-a-java-app-with-maven/
Build a mini Pipeline

41. Extend the mini Pipeline

42. 42
Extend the mini Pipeline

43. 43
Extend the mini Pipeline

44. 44
Extend the mini Pipeline

45. 45
 Head over to:
- https://github.com/jpdecastro/simple-java-maven-app.git
 Check-out Branch
- Sonar-pre-integration
Extend the mini Pipeline

46. Titel
Onderwerp
Verantwoordelijke afdeing, personen.
Datum
Thank you for your
attention!