Juni Mukherjee, Consultant CI/CD, Lifelock Continuous Delivery (CD) is important for a business to be sustainable. However, CD is not a discipline on it’s own (not yet), and the science behind it is rarely covered in schools. The intended audience for this talk are engineers, architects and technical managers who are starting out to build Continuous Delivery Pipelines, or are seeking to improve ROI on their existing investments. Every company aspires to sustainably flow their ideas into the hands of their customers, and reduce Time2Market. This talk goes into the heart of this burning topic and provides technical recipes that the audience can take away. This talk would cover: a) Domain Driven Design (DDD) for CD, based on concepts authored by Eric Evans The Continuous Delivery Pipeline can be modeled as a domain. b) How the CD Pipeline, along with its assets, can be orchestrated with Jenkins The Continuous Delivery Pipeline domain can be orchestrated with Jenkins 2.0, aka Pipeline-as-code. Each box in the model could be authored as a stage in Jenkinsfile. c) Pipeline patterns and anti-patterns There are some trends that are consistently observed in the industry. d) KPIs to measure ROI from the Pipeline “Show me the money!”. This is the “Jerry Maguire moment”, whereby the ROI is demonstrated.

1. November 15, 2016
Continuous Delivery Pipeline –
Patterns and Anti-patterns
Juni Mukherjee (@JuniTweets)
Consultant, CI/CD, LifeLock
(Views are my own.)

2. November 15, 2016

3. November 15, 2016

4. November 15, 2016
Domain-driven Design (DDD) for Continuous Delivery
Thank you Eric Evans for DDD!
Entity : Defined by ID, not attributes Value Object : Defined by attributes, no ID
Aggregate : Collection of objects Domain : Sphere of activity and influence
Model : System of abstractions Domain Event : Domain experts care for
Ubiquitous Language : Shared language Domain Services : Shared functionality
Connect the implementation to an evolving domain model
Continuous Delivery is a journey, not a destination.

5. November 15, 2016
Domain Model Integrity – Bounded Context, Context Map
© 2016 CloudBees, Inc. All Rights Reserved

6. November 15, 2016
Fragmentation, Blurred Edges, Bounded Context, Context Map
© 2016 CloudBees, Inc. All Rights Reserved
Node,
Java,
iOS,
Android,
Database,
::::::
::::

7. November 15, 2016
Domain Model Integrity – Ubiquitous Language
© 2016 CloudBees, Inc. All Rights Reserved

8. November 15, 2016
Ubiquitous Language – [Soft | Hard | Firm]ware, Embedded, IoT
Component
The smallest distributable and
testable unit
Unit, SCA – Linter, SCA – Security
Vulnerabilities
Modules, Libraries
Subsystem
The smallest deployable and
runnable unit
Functional (Security,
I18N, L10N, …), Performance
JAR | IPA | APK | Emulators |
Simulators …
System
Loosely coupled subsystems
Integration (Interfaces,
Network), Performance
JAR & IPA & APK & Real Devices
& Accessories …
Rate of Change, Supply Chain

9. November 15, 2016
Domain Model Integrity – Continuous Integration
© 2016 CloudBees, Inc. All Rights Reserved

10. November 15, 2016
Continuous Integration, Continuous Delivery, Value Stream Map
Product : System Under Test (SUT) Configuration : Application, Environment
Test : Unit, Static, Functional, Integration, Perf Infrastructure, Platform: Infra-As-Code, *aaS
Pipeline-As-Code : Dockerized Jenkins 2.0, Jenkinsfile (Process-As-Code), Shared Kernel (Utils.groovy, Libs)
VSM: Automate ONLY the value-adding steps. Discard the rest.

11. November 15, 2016
MVP - Continuous Delivery Pipeline, Slice over Dice
© 2016 CloudBees, Inc. All Rights Reserved
Product Slice : System Under Test (SUT) Configuration Slice : Application, Environment
Test Slice : Unit, Static, Functional, Int, Perf Infrastructure, Platform: Infra-As-Code, *aaS
Pipeline-As-Code : Dockerized Jenkins 2.0, Jenkinsfile (Process-As-Code), Shared Kernel (Utils.groovy)

12. November 15, 2016
Domain Model Integrity – Big Ball of Mud (And Tests Too?)
© 2016 CloudBees, Inc. All Rights Reserved

13. November 15, 2016
Pipeline – Graph – Tightly Coupled Product Architecture

14. November 15, 2016
Domain Model Integrity – Separate Ways
© 2016 CloudBees, Inc. All Rights Reserved

15. November 15, 2016
Pipeline – Linear – Independently Deployable Artifact

16. November 15, 2016
Death by a thousand test-types!
… And by a thousand environments!

17. November 15, 2016
Domain Model Integrity – Customer/Supplier Teams
© 2016 CloudBees, Inc. All Rights Reserved

18. November 15, 2016
Customer Supplier - Pipeline Design Pattern

19. November 15, 2016
Domain Model Integrity - Conformist
© 2016 CloudBees, Inc. All Rights Reserved

20. November 15, 2016
Conformist – Pipeline Design Pattern

21. November 15, 2016
Domain Model Integrity – Shared Kernel, Anti-corruption Layer
© 2016 CloudBees, Inc. All Rights Reserved

22. November 15, 2016
Shared Kernel, Anticorruption Layer
Domain Services,
Services Architecture,
Cloudy with a chance of
sharp interfaces
Network Latency,
Circuit Breaker

23. November 15, 2016
Pipeline-as-a-service: Scrum Teams sign a contract!
1. Process drives Architecture. Process drives tools.
2. Pipeline is a product, based off the Services Architecture.
3. The suite of polyglot Domain Services, with sharp interfaces, could be developed
by anyone in the organization, based off protocol.
4. Exact interfaces should declare exact intent. Should maintain existing interfaces so
that customers don’t experience service disruption.
5. Segregation/Separation of duties is the concept of having more than one person
required to complete a task. It is an internal control intended to prevent fraud and
error. It does NOT mean Human Being A does not trust Human Being B and hence
starts a new department of clicking buttons.
6. Should enable Pipeline customers to make choices, so that Scrum Teams could
control their own destiny.
Scrum Teams control their own destiny

24. November 15, 2016
Domain Model Integrity – Published Language
© 2016 CloudBees, Inc. All Rights Reserved

25. November 15, 2016
Published Language – DSL, It’s groovy!, 1-800-Plumber
Unmanageable string of jobs you’ve become,
Pipeline you must be,
Declarative, versioned and ephemeral become you must,
Or the dark side won’t set you free.
Pipeline analytics report you must,
In the groove you must get,
Make happy our engineers you must,
Don’t make them fret.
Jenkinsfile / Jenkins 2.0
node ("${AGENT}") { }
stage ‘deploy’
timeout (time:2, unit:'DAYS')
{input message: ’Proceed?”, submitter:
’Operations’}
stage ‘functional, performance, security test’
parallel ( parallel_task_stage_sauce : {
}, parallel_task_stage_blazemeter : {
}, parallel_task_stage_appspider : { })
try {}
catch (InterruptedException x) { slackSend color: '#008000',
message: ”” }

26. November 15, 2016
Domain Model Integrity - Flying colors!
© 2016 CloudBees, Inc. All Rights Reserved

27. November 15, 2016
KPIs – Show Me the Money!
What can be measured, can be fixed!

28. November 15, 2016
On Closing : Conway’s Law, Maya Angelou’s Human Family
“Organizations which design systems ... are constrained to produce
designs which are copies of the communication
structures of these
organizations.”
Melvin Conway
“I note the obvious
differences between
each sort and type,
We are more alike,
my friends, than we
are unalike.”
Maya Angelou

29. November 15, 2016
Thank you AllDayDevOps,
Community, Sponsors and
Supporters!
Juni Mukherjee (@JuniTweets)