Continuous Integrations with Jenkins

Introductory presentation for EVRY employees about Continuous Integrations and Jenkins CI

Transcript

1. Continuos Integration with Jenkins ! HANS KRISTIAN FLAATTEN
2. ! 2 Ask questions in the chat
3. ! Agenda OPTIONAL SUBHEADING • Continuous Integration (CI) • The CI Server • Jenkins CI • Jenkins Pipelines • DEMO • Continuous Deployment (CD)
5. ! 5 Continuous Integration Integrating code back to a shared mainline • Automate build & test • Ensure reproducibility • Detect errors early • Improve quality • Reduce cost
6. ! 6 Pull Requests & Merges
8. ! 8 The CI Server 1. Fetch code from source control 2. Build and test the software 3. Notify on success/failure
9. ! 9 The CI Server (cont) • General purpose • Language, framework & tooling • Good integrations • Source control & team communication • Support complex build pipelines • Store artefacts • Run deployment • Be efficient
10. ! 10 Different CI Servers Hosted/Cloud On Premise
11. ! 11 Jenkins CI • General purpose automation server • Free and open source • Works on any plattform • Released in 2005 • Sponsored by CloudBees • The largest CI plugin system https://jenkins.io/
12. ! 12 The good, the bad & the ugly • You can do anything • You can do ANYTHING • Customisability vs. ease of use • It is still a JAVA application
13. ! 13 Some terminology • Job - a unit of work for a project • Pipeline • View - user defined collection of jobs or a workflow • Master - the central Jenkins master, does job scheduling • Agent - executes one or more jobs within slots (executors) • Workspace - the working area where a job is carried out
14. ! 14 Jenkins CI Group of Agents Agent Agent Master SSH / JNLP
15. ! 15 Node.js Foundation Jenkins 150 servers 8 CPU architectures 18 operating systems 30 minutes
16. ! 16 Traditional Jenkins Jobs ! " # # ! # " # Job Config Secret $ $ Code " Jenkins SCM "
17. ! 17 Traditional Jenkins Jobs • Web UI centric • All jobs must be configured manually • Overhead for multiple (smaller) projects • Source code and job must be kept in sync • Chaining multiple jobs becomes messy • Build • Test • Deploy
18. ! 18 New Jenkins Pipelines ! " % Pipeline Config Secret $ Code ! " % $
19. ! 19 New Jenkins Pipelines • One job per repository • Jenkins jobs as code • Jenkinsfile in source code repository • Always in sync with the code • All changes are logged • Written in Groovy • Declarative syntax • Domain Specific Language (DSL) • Extended by Shared Libraries
20. ! 20 Pipeline Terms • Node - where to run a set to stages • Stage - a single stage in a Pipeline • Step - a single task to be executed
21. ! 21 Jenkinsfile node('any') { stage('Build') { sh 'make' } stage('Test') { ... } stage('Deploy') { ... } }
22. Demo
23. ! 23 Wait for user input node('any') { stage('Build') { sh 'make' } stage('Test') { ... } stage('Deploy to test') { ... } input('Ready for production?') stage('Deploy to prod') { ... } }
24. ! 24 Continuous Delivery (CD) • Delivery = deployment • Deploy when all tests pass • Continuous Integration is a requirement • Repeatable • Automated • DevOps / Microservices
25. ! 25 Principles • Process must be repeatable, reliable • Everything needs to be automated • If it hurts; do it more often • Deploy often and smaller changes • Source control everything • Done means released • Build quality in • If you build it; you deploy it
26. Questions?