Octopus Deploy makes it effortless to push your code from development through to test, staging, and production. Octopus is built to make your deployments successful, but sometimes deployments go wrong even with the best planning.
A robust rollback strategy is key to any deployment strategy. In this webinar, we’ll cover best practices for IIS deployments, Tomcat, and full stack applications with a database. We’ll also discuss how to get the rollback strategy right for your situation.
Join Bob Walker, VP of Customer Solutions, and Shawn Sesna, Senior Solutions Architect, to learn:
- Common problems in production that cause the need for a rollback
- Strategies for rolling back and forward
- Considerations when rolling back databases
Meet the speakers
VP of Customer Solutions – Octopus Deploy
Bob Walker is VP of the Customer Solutions Team at Octopus Deploy. He joined Octopus Deploy in 2018 as a Solutions Architect, where he focused on helping customers succeed by using Octopus. Bob’s background is in .NET development, but his passion has expanded from writing code to creating full CI/CD pipelines and implementing DevOps practices.
Senior Solutions Architect – Octopus Deploy
Shawn Sesna is a Senior Solutions Architect at Octopus Deploy. He helps our customers by providing advice, trouble-shooting features, analyzing instances, and creating examples on samples.octopus.com. He’s also written many [blog posts] (https://octopus.com/blog) on maximizing your use of Octopus Deploy. Before Octopus, Shawn was with the Washington state government for 21 years. His positions included developer, database administrator, configuration manager, and DevOps engineer. In 2015, Shawn implemented Octopus Deploy, replacing a homegrown solution he developed in C#.