This morning on #c9d9 we talked about Process-as-Code.
DevOps at scale requires predictability and consistency. Your application code is versioned. Infrastructure-as-code defines your environments. But what about the process?
How do you define your processes as code? What are some use cases and best-practices for ensuring your automation is versionable, testable, and repeatable.
Watch the replay of the episode :
This episode features:
Author of “Continuous Delivery Pipeline – Where Does It Choke?“.
@JuniTweets | techbeacon.com/contributors/juni-mukherjee
J. Paul Reed has over 15 years experience in the trenches as a build/release engineer, working with such companies as VMware, Mozilla, Symantec, and Salesforce. He speaks internationally on release engineering, DevOps, operational complexity, and human factors.
@jpaulreed | jpaulreed.com
Mark is learning how to make himself dispensable with automation and continuous data…
On the next episode of Continuous Discussions:
Episode 49: Deployment Patterns
Join us on September 6, to discuss best practices for advanced deployment patterns and deployment pipelines.
This episode will feature:
@vfarcic | technologyconversations.com
Continuous Discussions (#c9d9) podcasts air every other Tuesday. See all episodes here.
Latest posts by Anders Wallgren (see all)
- Continuous Discussions (#c9d9) Podcast, Episode 65: ChatOps and DevOps - March 28, 2017
- Continuous Discussions (#c9d9) Podcast, Episode 64: Docker & Microservices at Scale - March 14, 2017
- 4 Rules for Microservices and Software Delivery - March 1, 2017