Continuous Delivery with DeployHub and Chef or Puppet 

Include infrastructure configuration management with your application

DeployHub allows you to use continuous delivery to incorporate infrastructure configuration management changes with your existing Chef or Puppet processes creating a complete application release automation package.  Incorporating the IT stack changes into the application package is the easiest way to guarantee a successful Continuous Deployment process that addresses the entire ecosystem. Changes to the IT Stack pushed by continuous delivery are versioned and traced along with your application deployment keeping a history of all the moving parts in a central location.  You can easily rollback or roll forward code changes with the infrastructure changes and version the combined package. Using DeployHub with Chef or Puppet does not require that you create an RPM for your Application Stack. Your DeployHub workflow can be defined to coordinate the IT stack updates, calling out to Chef or Puppet, with the Application stack updates in the correct order.    

DeployHub integrated with Chef and Puppet

DeployHub supports Chef or Puppet by allowing you to define your existing Chef and Puppet processes as a DeployHub Component and Action. DeployHub will call your Chef or Puppet process as part of your application deployment and track any changes to those processes over time.  Using existing IT configuration management processes allows you to jump start your release process without replacing the work you have already.   

 

 

 

EcoSystem

Jenkins continuous delivery CloudBees continuous delivery Chef continuous delivery Puppet continuous delivery Ansible and continuous delivery Cloud Foundry and continuous delivery IBM Websphere and continuous delivery Apache Tomcat and continuous delivery GitHub and continuous delivery Subversion and continuous delivery
Go to top