Understand the advantages of using DeployHub for continuous deployments and Application Release Automation in comparason to traditional methods.
How to leverage DeployHub, IT Automation (Ansible, Chef, Puppet), or Jenkins and CloudBees for stronger continuous delivery.
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 needed for continuous deployment.

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 automatically updates configuration files even when embedded into your jars or wars. Deploying to different states in your continuous delivery pipeline requires that these configuration files be updated for the appropriate location.

Learn how to execute a procedure on a remote endpoint as part of a component or software deployment install step. This process automates your continuous deployment across the continuous delivery pipeline in a repeatable manner.

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.