Continuous Deployment with Jenkins Pipelines

! DEVOPS BERGEN MEETUP PUBLIC HANS KRISTIAN FLAATTEN AUG, 2017
Continous Deployment & Jenkins

Devopsdays Oslo NOVEMBER 1-2, 2017

! 3 About me • Hans Kristian Flaatten • Married
and two boys • Informatics @ NTNU • Platform Engineer • DevOps Practice Lead • Node.js Foundation Member

!  CI / CD  Git  Team 
 Container Platform  Monitorering  Errors  Logging  Chat App Platform 2017

! Agenda • Continuous Integration (CI) • The CI Server
• Jenkins CI • Continuous Deployment (CD) • Continuous Delivery • Infrastructure as Code • Jenkins Pipelines • DEMO

You build it, you run it –Werner Vogels, CTO Amazon
! !

! 8 Continuous Integration Integrating code back to a shared
mainline • Automate build & test • Ensure reproducibility • Detect errors early • Improve quality • Reduce cost

! 10 Pull Requests & Merges

! 11 Notifications

! 13 The CI Server 1. Fetch code from source
control 2. Build and test the software 3. Notify on success/failure

! 14 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

! Tests Required

! 16 Different CI Servers Managed On Premise

! 17 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/

! 18 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

! 19 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

! 20 Jenkins CI Group of Agents Agent Agent Master
SSH / JNLP

! 21 Node.js Foundation Jenkins 150 servers 8 CPU architectures
18 operating systems 30 minutes

! 22 Traditional Jenkins Jobs ! " # # !
# " # Job Config Secret $ $ Code " Jenkins SCM "

! 23 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

! 25 Continuous Delivery (CD)

! 26 Continuous Deployment

! 27 Blue/Green Deployment

! 28 Canary Release

! 29 Feature Toggles

Orchestration

! 31 Infrastruktur as Code (IAC)

! 32 New Jenkins Pipelines ! " % Pipeline Config
Secret $ Code ! " % $

! 33 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

! 34 Pipeline Terms • Node - where to run
a set to stages • Stage - a single stage in a Pipeline • Step - a single task to be executed

! 35 Jenkinsfile node('any') { stage('Build') { sh 'make' //
this is a step } stage('Test') { ... } stage('Deploy') { ... } }

! 36 Wait for user input node('any') { stage('Build') {
sh 'make' } stage('Test') { ... } stage('Deploy to test') { ... } input('Ready for production?') stage('Deploy to prod') { ... } }

! 38 Challenges • Testing Jenkinsfiles • Use the online
editor • Groovy Standbox • Repetition between projects • Make shared libraries • Wrapping errors in try/catch • Fixed in newer declarative pipelines

Taking it one step further… !

! 40 +

! 41 Jenkins + Docker Jenkins " # Jenkinsfile #
# Stages 1 2 3 install build test

EMAIL MOBILE TWITTER " ! (+47) 402 85 501 @Starefossen
[email protected]

Continuous Deployment with Jenkins Pipelines

Continuous Deployment with Jenkins Pipelines

More Decks by Hans Kristian Flaatten

Other Decks in Technology

Featured

Transcript