Performing a pre-flight of your deployment tests the deployment logic and access availability. Pre-flights reduce errors especially when initially defining your Application and the associated Components.

A series of checks is performed by DeployHub as soon as an Environment is selected from the list in the dialog box. If there are problems, DeployHub prevents the deployment from taking place. For instance, when the User initiating the deployment doesn’t have permission to deploy to the selected Environment, or when the Calendar for the selected Environment has another deployment scheduled. If problems are found, the OK button is greyed out and an error message is displayed. Otherwise the window will disappear and messages concerning the deploy will be visible by clicking first on the Timeline tab, and then clicking on the topmost Deployment Number in the resulting list. A window will appear with seven tabs:




Files display all files that have been deployed during the execution of the deployment. Error messages may appear after the deployment has begun concerning things that DeployHub is not aware of during the initial check, such as missing files in a Repository or an Endpoint being offline.


This tab displays all information concerning the progress of the deployment, including Repositories that are being accessed, files that are being deployed, which Endpoints are being deployed to, etc. As it progresses, clicking on the button in the upper right side of the button with the double-arrow icon will redraw this tab, allowing the User to follow the progress of the deployment.


This tab contains a list of all the steps that made up the deployment. Each step’s number is listed, along with the activity, such as deployment, post Action, etc.

Change Requests

(DeployHub Pro Only)

The Change Request tab shows enhancement requests and bugs that have been assigned to the selected Application. These will have been assigned to the Application earlier from one or more popular bug tracking systems, such as Bugzilla, Github, and Jira.


This tab contains 8 basic fields with basic information concerning the deployment; Application Name, Environment Name, Deployed By, Stared, Finished, Time Taken, Exit Code (0 for a successful deployment, an error code for any failed deployment), and Exit Status (error text for any failed deployment).


This tab shows bar and pie graphs which represent the time taken for each deployment step.

Feedback Loop

This tab displays a graphical representation of the DeployHub objects that were used in the deployment process, beginning with Change Requests and moving through Components, Applications, and Environments. Each object is represented by a different colored box containing the objects name, with arrows to show which Components belong to which Applications, which Applications were deployed to each Environment, etc.

NOTE: The information in all four tabs will be updated during the display, so clicking on the tabs will redraw them as the deploy progresses.