As teams have adopted continuous delivery practices to improve the velocity with which they are able to deploy applications, many have found it difficult to scale these processes across their environments. Between different programming languages, operating systems, runtime environments, and application architectures, it's not uncommon to have dozens, if not hundreds, of different ways to build, deploy, and manage applications in a single organization, each of which must be accounted for explicitly within pipeline tools like Jenkins.
Chef's approach to addressing this increasing complexity is to automate application definition itself with Chef Habitat. By providing a unified automation framework for application lifecycle management, uniform pipelines can be built even in a vastly heterogeneous estate. In this webinar, we'll showcase several practical examples of how Chef can help drastically simplify your Jenkins configurations, even as you manage diverse applications and deployment strategies.