This document discusses automating the software development process from check-in to deployment in the cloud. It describes having a build server detect code changes, run tests and build the software. The final product is stored on a cloud file server. The build server then generates a custom boot script to launch a new instance and deploy the code. The goal is to remove human interaction from this process and have it run automatically on each check-in.

1. @jamesrcounts | @paulwhitmer

2. Legacy Code Expert
Full Stack Consultant
C#/VB/Perl/AngularJS/Node/Cloud

3. Full Stack ASP.NET MVC
C#/AngularJS/NodeJS/Cloud
Linux/Windows
DevOps TIG Mentor

4. The goal is to deliver new features and
not worry about the servers. Increasing
value to our customers.

5. A little history
Go back to basics, when high level tools fail to
deliver
How do we do it now?
Build
Deploy
Remove human interaction

6. Automatic: continuous integration on check-ins
Check-in frequently to get feedback more often
Create fast builds to tighten up the feedback cycle
Reveal any hidden assumptions about your build

10. Developer makes changes and checks in
Build server detects changes and agent in cloud runs tests
and builds software
Final product is zipped up and stored on cloud file server
Build server generates a custom boot script from a
template and launches a new instance to kick off the
deploy

11. Where to find the code
Firewall configuration
Security Roles
Network/VPN
configuration
Remote access keys
So many details… automate them!

12. Load baseline instance with custom boot
script
Pull and run pre-built code from online
file storage
Connect to load balancer

13. Download my app, unzip, and
run app
Add thy self to load balancer and
wait to become healthy
Tell load balancer to remove
other instances with a different
version
Tag thy self
Wait ten minutes then start
"Death Cron”
It’s another script!
A generic script that the boot script
invokes with parameters.

14. No human needs to kickoff a build/deployment
Scripts are built from template for each
environment
Environment itself has been mostly built from
script as well
Self cleaning instance destruction

15. Runs every minute
Am I attached to the load
balancer?
No?
“Amazon, please kill me”
Yes!
“The world loves me, keep going
and check it again in a minute”
aka "Death
Cron"

16. High level tools promise magic, but can deliver their
own set of problems
Beanstalk
Cloudformer
Docker
When a tool doesn’t deliver, kill it
Revisit the tool with a better understanding of
underlying mechanics.