For episode 35, the crew takes a look at a core component of continuous delivery: the application update mechanism. We talk a bit about our collective experiences supporting update paths, how some of the players in our industry conduct their updates, and whether or not that’s actually good for customers, or it’s just a myth we hear parroted constantly. We also take a look at a couple of case studies related to continuous delivery transformations, and some myths around the implementation details of continuous delivery, ultimately trying to figure out, whether it’s customers, engineering teams, release teams, or ops teams, are the way we do updates today:
Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, and EJ Ciramella, aka @eciramella for the discussion, plus a the last couple of weeks in News & Views and a (bunch of!) tool tips!
- 1:28 – News & Views
- GMail and Google Apps taken offline for a few hours, due to a configuration glitch
- The Onion piles on Google’s pain
YahooHotmail user receives thousands of emails an hour, possibly due to this bug
- Docker raises $15 million in latest investment round
- Attackers using unencrypted Windows crash dumps to craft exploits
- Among other things, Windows knows what devices, including your phone, you plug into your PC
- The rise of the “USB condom“
- Developer creates interactive map of the Github universe
- 9:58 – Main Segment: Continuous Deployment… or Annoy-ment?
- 52:54 – Tool Tip
- ChefConf in April
- Config Management Camp EU in Belgium in February
- Configuration Management DevRoom at 2014 FOSDEM
- Monitorama coming to Portland in May in 2014
- Mountain West DevOps in Salt Lake City in March
- Check out devopsconferences.com for a more conferences
Youssuf introduces us to jq (not “jk!”)
What’s your opinion, as a customer, on constant updates? Silent updates?
What application architecture and testing issues have you run into while trying to adopt continuous delivery?
Join the discussion!