DevOps Deployments-as-a-Service


DC Continuous Integration, Delivery, and Deployments


Matt Makai / @mattmakai


codingacrossamerica.com

March 9 - August 9

Driving

Miles driven

Coding

Meeting w/tech companies

DevOps Deployments-as-a-Service

DevOps? Deployments? Services?


 
 
 

Programming ecosystems?

Happy with current deployments?

Improvements?


 
 
 

Using services for deployments?

Ideal workflow

Ideal workflow

General attributes

  • When something breaks, you know
  • Minimal maintenance time overhead
  • Metrics show progress over time
  • Confidence to always deliver a quality application

Where the process breaks

  • Uncertainty over benefits
  • Unclear how to set up
  • Missing links in execution
  • Difficulty provisioning environments

Services

General advantages

  • Saves (expensive) developer time
  • Minimal maintenace overhead
  • Opinionated
  • Company focused on product

General disadvantages

  • Lose control over data
  • Hosting fees
  • Opinionated
  • Long-term viability?

Continuous Integration

Circle CI

Travis CI

Atlassian Bamboo

CloudBees Hosted Jenkins

Semaphore (Rails)

Testing

BrowserStack

CrossBrowserTesting

Monitoring

New Relic

CopperEgg

Pingdom

PagerDuty

Build Process

Code Climate (Ruby)

Factor.io

Tinfoil Security

Learning More

Mindset

  • Research when not under pressure to immediately integrate
  • Ask "What problem can this service potentially solve?"

Mindset

  • Background and philosophy
  • Openness about their solution approach
  • Bookmark services and arguments for and against

"Push" sources

Geckoboard Widgets

Ducksboard Integrations

Resources

Thank you!