Subscribe for more content: http://vid.io/xqZ4
Check out our other videos: http://vid.io/xqZ9


I was down in Pasadena, CA for the SoCal.NET Users Group on Sept 1 for the "Building a Release Pipeline Talk" given by Mike Roth. In his talk, Mike explains what a release pipeline is, discusses each component, how to implement them and what to watch out for. Mike also covers tooling for each processes.

Talk description

Shipping is a feature! But what does that really mean? While it is exceptionally easy to write code, it has become exceptionally hard to deploy it in a reliable fashion at mass scale and deal with complex architectures.

Do any of the following happen to you when you deploy?

*The build version is incorrect?

*The build you shipped has "hidden" and "untested" features?

Your system works fine rolling forward, but rolling backward is a pain.

Sending code to production always feel like Russian Roulette, waiting for IT to inform you that there is a fatal issue and they have to roll back and try the deployment again at the next release window, which by the way is another month!

What if I told you that there is a way to build a release pipeline that will give your team, your managers and best of all your stakeholders and customers confidence in every release, and that the next fix to production won't result in another downtime window, or that killer feature or initial launch will go without a hitch or at the very least develop a process to fix the build quickly and without lengthy downtime windows? It's possible!

In this talk I will introduce you to the idea of the "Release Pipeline" and how to build one. We will focus on actual real world case studies using an example that includes one of the top 100 most trafficked website on the web. We will also visit examples on how small shops can gain stability in deploying to production.

Blog: http://www.michaeltroth.com
SoCal .NET: http://www.meetup.com/SoCalDevNet/