As I wrote in my previous blog post, “Using Serena Release Automation and Infrastructure as Code to Build Your DevOps Solution,” Puppet can play an important part when used in conjunction with Serena solutions.
Plenty of enterprise customers were in attendance and there was a great session on Puppet Enterprise at Scale by Benjamin Irizarry of Bank of America, which is a good example of how infrastructure as code initiatives are no longer confined to start-ups.
DevOps and Continuous Delivery were hot topics, with an excellent session by Eric Shamow of Puppet Labs on Continuous Delivery. View the presentation.
The one thing that stood out at PuppetConf is that process orchestration is still a big problem, as illustrated in Eric’s demo. Using Jenkins plus plugins makes for a simple demo for Continuous Delivery but it doesn’t change the fact that CI tools are build-centric and there is much more to a release than the output of a build. Eric did not suggest that using Jenkins to drive a continuous delivery pipeline was good for production, just that it made for an easy demo.
The lack of a good orchestration framework is something that we frequently hear from prospects and customers with release management problems. Serena Release Control is a key piece of a modern release management solution, providing auditability, visibility and control of a release process, and integrating with commonly used tools in both the Dev and Ops space. This visibility and auditability is possible because in Serena Release Control everything flowing through the system isn’t a build. We orchestrate releases, capturing all of the data that is associated with a release and reporting on it in the context of a release. CI tools form a critical part of a release management process; they just aren’t a good choice for orchestrating your release process. See how Serena Release Control works within our release management solution.