The document discusses the quest for continuous delivery at Pluralsight, outlining the importance of delivering ideas to users quickly and the roles involved in the process such as delivery teams and developers. It describes the risks and benefits of small, automated releases and details Pluralsight's technology stack, feedback processes, and tools for implementing continuous delivery. Additionally, it highlights future plans for automated performance and security testing, as well as improvements to server management and staging environments.

1. The Quest for Continuous
Delivery at Pluralsight
Mike Clement
@mdclement
mike@softwareontheside.com
http://blog.softwareontheside.com

2. Overview of CD
Pluralsight today
The future

6. If somebody thinks of a good
idea…

7. …how do we deliver it to users as
quickly as possible?
Continuous Delivery, Introduction

9. Done?

10. Done is released

11. Deployment
Provisioning and managing the environment in which your application
will run (hardware configuration, software, infrastructure,
and external services).
Installing the correct version of your application into it.
Configuring your application, including any data or state it requires.
Continuous Delivery, Chapter 1

14. Who?

15. Delivery Team
Product
Testers
Build
Ops
Support
Developers

16. What?

17. Managing Risk
Small releases
Automated tests
Visible
Repeatable
Reliable
Predictable

18. Why?

19. Reducing Errors
Lowering Stress
Deployment Flexibility

20. How?

21. Every change that is made to…
…triggers the pipeline.
Continuous Delivery, Introduction
configuration
source code
environment
data

22. https://www.chef.io/images/chart-continuous-delivery.png

24. Version control everything that can change
configuration files
scripts to create databases and their schemas
build scripts
test harnesses
development environments
operating system configurations

25. Feedback Process
• Build
• Unit tests
• Coverage/static analysis
• Acceptance tests
• “Non-functional” tests (capacity, security, availability)
• UI tests

27. Practices at Pluralsight

28. Technology Stack
.NET (C#)
Angular JS
RavenDB
Homegrown XML based DB
IIS/Windows
Windows Services

29. XP Simple Design
Passes all tests
Clear, expressive, consistent
No duplication
Minimal

30. Pair Programming

34. Feedback Process
• Build
• Unit tests
• Coverage/static analysis
• Acceptance tests
• “Non-functional” tests (capacity, security, availability)
• UI tests

35. Tools at Pluralsight

36. mSpec

41. Feedback Process – TeamCity
• Build
• Unit tests
• Acceptance tests
• UI tests

42. Site Management tool

45. Octopus
• Variables – application configuration
• Web.config transforms
• NuGet package with application
• Before/after scripting

47. Hosted ViaWest
• “Private” Cloud
• Commodity virtual hardware
• Moving to…

49. AWS (EC2)
• Commodity hardware
• Ops configured

54. Where are we going next?

55. Every change that is made to…
…triggers the pipeline.
Continuous Delivery, Introduction
configuration
source code
environment
data?

58. Every change that is made to…
…triggers the pipeline.
Continuous Delivery, Introduction
configuration
source code
environment
data

60. {
"Title": "AngularJS Fundamentals",
"ShortDescription": "This course will teach you the AngularJS fundamentals required to create testable, MVC-style single page
applications with AngularJS.",
"Description": "In this course you will learn how simple it is to use AngularJS to create maintainable and testable single page
applications. You will learn how to: bootstrap your AngularJS application; use AngularJS markup and expressions; create and use
controllers; use built-in services and create custom services; turn your application into a SPA using routing; and create your own
custom elements and handle events using directives. You will also learn how AngularJS allows you to do all thing using test-driven-
development.",
"PublishedOn": "2013-05-17T00:00:00.0000000",
"ShowTranscripts": true,
"Level": "Intermediate",
"RecentViewTime": 9542531,
"Subcategory": "",
"MaterialsFilePublishDateUtc": "2014-04-11T12:34:15.0000000",
"TotalRating": 7861,
"TotalNumberOfRaters": 1775,
"AllowAnonymousExerciseFiles": false,
"AllowFreeAssessments": false,
"Name": "angularjs-fundamentals",
"Category": {
"CategoryName": "javascript",
"CategoryTitle": "JavaScript"
},
"Duration": 22918,
"ModuleRefs": [
"coursemoduledtos/joe-eames/angularjs-fundamentals-m1-intro",
"coursemoduledtos/joe-eames/angularjs-fundamentals-m2-markup-controllers",
"coursemoduledtos/jim-cooper/angularjs-fundamentals-m3-services",
"coursemoduledtos/jim-cooper/angularjs-fundamentals-m4-routing",
"coursemoduledtos/jim-cooper/angularjs-fundamentals-m5-directives",
"coursemoduledtos/joe-eames/angularjs-fundamentals-m6-testing"
]
}

63. Feedback Process
• Build
• Unit tests
• Coverage/static analysis
• Acceptance tests
• “Non-functional” tests (capacity, security, availability)
• UI tests

64. Immediate Future
• Server Management as Code
• More saltstack
• Salt pillars with application code
• Raven to Cassandra
• automate modifications to database schema in Cassandra
• Better staging environment
• SOX
• Automation over Documentation
• Enforcing Traceability
• Change Management
• Better live testing/monitoring – New Relic

65. A little further out…
• Automated performance testing on stage on every build
• Automated security testing on stage on every build
• Continual automated performance testing on live
• Continual automated security testing on live
• Immutable infrastructure
• Continuous Deployment/Release?

71. Resources
• Jez Humble - http://continuousdelivery.com/
• Gene Kim - http://www.realgenekim.me/
• Kevin Behr - http://www.kevinbehr.com/

72. Mike Clement
• @mdclement
• mike@softwareontheside.com
• http://blog.softwareontheside.com
• http://agilecodegames.com
• https://github.com/mdclement
• Utah Software Craftsmanship
• http://utahsc.org
• @utahsc
• We meet the first Wednesday at Pluralsight-Lehi
• http://agileroots.com