Understand the advantages for using DeployHub for continuous deployments and Application Release Automation compared to traditional methods of software deployments.
How to leverage DeployHub, IT Automation (Ansible, Chef, Puppet), Jenkins and CloudBees for a stronger continuous delivery foundation.
This whitepaper shows how to use your Jenkins Pipeline to orchestrate continuous deployments to production with DeployHub.
How using DeployHub to take over continuous deploy allows your continuous delivery process to scale across the pipeline.

Demos and Setup

Tips and Tricks

Use Domains to create self-service around continuous deployments. Domains are key to sharing common objects, avoiding redundant scripting and providing the ‘pre-check’ process that is needed to keep the continuous deployment process flowing.

DeployHub supports the ability to jump between any two software releases (4.1 to 4.8 for example) incrementally for managing software deployment. No monolithic deployments are needed. This includes updates to the database.

DeployHub can automatically update your configuration files, even when they are embedded into your jars or wars. Deploying to different states in your continuous delivery pipeline will require that these configuration files be updated for the appropriate location.

See how to create a procedure that executes on a remote endpoint. A procedure is executed as part of a component or software deployment install step. This is used to automate your continuous deployment process across the continuous delivery pipeline in a repeatable process.

This Demo shows how you can bring z/OS into the Jenkins Continuous Delivery Pipeline, creating a ‘super’ Application Package that deploys artifacts from z/OS, and in this demo, Windows.