Download to read offline
Uploaded byDevOpsDays Baltimore
Deploying 30 times a day, and making sure everything stays 200 OK by Eric Sigler
The document discusses various aspects of continuous improvement and deployment, emphasizing the importance of automation and simplified rollout processes. It suggests that 100% test coverage is unnecessary and highlights the need for fair workload distribution among engineers. The content includes references to resources such as the 2016 State of DevOps Report and practical advice on managing deployment practices.
More Related Content
Similar to Deploying 30 times a day, and making sure everything stays 200 OK by Eric Sigler
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
Deploying 30 times a day, and making sure everything stays 200 OK by Eric Sigler
- 1.
- 2.
- 3. @esigler How To DeployAt PagerDuty
- 4. @esigler CD in anutshell
- 5. @esigler OK, so Ineed to test & automate everything, right?
- 6.
- 7.
- 8.
- 9. Declare a Continuous Deploymentholiday @esigler
- 10. Declare a Continuous Deploymentholiday @esigler
- 11. “Ignore the engineer behindthe curtain” @esigler
- 12.
- 13.
- 14.
- 15.
- 16.
- 17. @esigler How To DeployAt PagerDuty
- 18.
- 19. @esigler Don’t need 100%test coverage Keep rollout simple to start Practice before writing tools Exercise coordination Be fair in workload
- 20. “The more theyoverthink the plumbing, the easier it is to stop up the drain.” @esigler