A DevOps Pipeline

@steveElsewhere PIPELINE A DEVOPS @steveElsewhere

@steveElsewhere ME

@steveElsewhere CONTEXT VALUE

@steveElsewhere WHY DO WE NEED A PIPELINE?

@steveElsewhere CREATING VALUE WHY WOULD WE SHIP 100 TIMES A
DAY?

@steveElsewhere ITERATION

@steveElsewhere PIPELINE SO, ABOUT THAT @steveElsewhere

@steveElsewhere ‣ NATURAL START AND END ‣ STARTS WITH SOURCE
CONTROL ‣ INITIATE WITH EACH CHANGE ‣ RUN IN PARALLEL AND/OR SEQUENTIALLY ‣ SUCCESS MEANS CODE IN PRODUCTION PIPELINE CHARACTERISTICS

@steveElsewhere CONTINUOUS DELIVERY CHANGE STABILIZE VALIDATE RELEASE

@steveElsewhere PROCESS CODE TEST BUILD DEPLOY

@steveElsewhere STAGES DEPLOY DIRECTLY CONTINUOUS INTEGRATION CONTINUOUS DELIVERY CONTINUOUS DEPLOYMENT

@steveElsewhere CRUCIAL? WHY IS IT @steveElsewhere

@steveElsewhere THE WALL @steveElsewhere

@steveElsewhere DOCKER LETS TALK ABOUT

@steveElsewhere CAVEATS LETS TALK ABOUT

@steveElsewhere A FEW PIECES

@steveElsewhere ADVANTAGES LETS TALK ABOUT

@steveElsewhere LIGHT WEIGHT REUSE CONSISTENCY WHY DOCKER? PUSH/PULL VERSIONING PORTABILITY

@steveElsewhere 1. RUN UNIT TESTS 2. BUILD THE IMAGE THAT
WE USE TO BUILD OUR APP 3. RUN THE BUILD CONTAINER AND COMPILING OUR APP 4. BUILD THE IMAGE THAT WE RUN AND DEPLOY 5. PUSH THE FINAL IMAGE TO A DOCKER REGISTRY OVERVIEW

@steveElsewhere SOME  PREREQUISITES

@steveElsewhere PROVISIONING AND CONFIG

@steveElsewhere OUTSIDE OUR CONTAINER

@steveElsewhere DOCKER TOOLBOX OR VIRTUAL MACHINE

@steveElsewhere BASE VOLUME BUILD RUN CONTAINER TYPES

@steveElsewhere OS SOURCE REPOS PACKAGES CLEANUP THE BASE CONTAINER

@steveElsewhere MINIMAL BARE OS FILE STRUCTURE FILES THE VOLUME CONTAINER

@steveElsewhere THE BUILD CONTAINER BASE CONTAINER CODE COPY COMPILE CLEANUP

@steveElsewhere BUILT CONTAINER RUN COMMAND THE RUN CONTAINER

@steveElsewhere CASCADE CHANGE CHANGE BASE REBUILD BUILD REBUILD BASE REBUILD
RUN RUN

@steveElsewhere QUALITY ASSURANCE

@steveElsewhere BEYOND BASICS

@steveElsewhere QUALITY ASSURANCE CODE COMMIT TEST ENV PRODUCTION TESTING Unit
Mock

@steveElsewhere CODE COMMIT TEST ENV PRODUCTION TESTING Regression Cross-Device Functional
Static Analysis Integration QUALITY ASSURANCE

@steveElsewhere QUALITY ASSURANCE CODE COMMIT TEST ENV PRODUCTION TESTING Exploratory
Acceptance Performance Smoke Security

@steveElsewhere QUALITY ASSURANCE CODE COMMIT TEST ENV PRODUCTION TESTING Smoke
A / B

@steveElsewhere QUALITY ASSURANCE TESTING Unit Mock TESTING Regression Cross-Device Functional
Static Analysis Integration TESTING Exploratory Acceptance Performance Smoke Security TESTING Smoke A / B

@steveElsewhere QUALITY ASSURANCE

@steveElsewhere CI ONSITE ‣ JENKINS ‣ GITLAB CI ‣ GO.CD
‣ STRIDER ‣ TEAM FOUNDATION SERVER

@steveElsewhere CI ONLINE ‣ SHIPPABLE ‣ CODESHIP ‣ CIRCLE CI
‣ TRAVIS ‣ APPVEYOR

@steveElsewhere BUILD ‣ DOCKER (LOCAL) ‣ PACKER (LOCAL) ‣ DOCKER
HUB ‣ QUAY.IO ‣ ANY CI TOOL

@steveElsewhere DEPLOYMENT PULL FROM HUB CONFIG MANAGEMENT

@steveElsewhere THE #! CODE CHANGE PUSH TRIGGER TRIGGER PULL TRIGGER

@steveElsewhere WHERE WE GO FROM HERE

@steveElsewhere AUTOMATION

@steveElsewhere THE BOTS AGE OF

@steveElsewhere COLLABO- TOMATION CHATOPS

@steveElsewhere VISIBILITY CHATOPS

@steveElsewhere MY ADVICE

@steveElsewhere THE EDGES THINK ABOUT

@steveElsewhere SCHEDULING STORAGE SERVICE - DISCOVERY OTHER CONSIDERATIONS: LOGGING MONITORING
NETWORKING

@steveElsewhere HEALTHCHECK ROLLBACK GRACEFUL FAILURE OTHER CONSIDERATIONS: SECRETS SCALING CRON

@steveElsewhere CHANGE AS LITTLE AS POSSIBLE GO H.A.M.

@steveElsewhere SPECIFICS AIM FOR

@steveElsewhere THINK ABOUT SECURITY

@steveElsewhere START NOW

@steveElsewhere THANK YOU! J.MP/TALKRESOURCES

A DevOps Pipeline

A DevOps Pipeline

More Decks by Steve Pereira

Other Decks in Technology

Featured

Transcript