Environments represent a collection of Endpoints used by a specific group of individuals. Each Application can have many Environments, commonly Development, Testing and Production. Environments are mapped to your continuous Delivery Pipeline stages.  

Environments and Domains

Environments are associated to a Domain. You can assign Environments to any level of Domain including the Global Domain. However, Environments are most commonly associated to a Project Domain. A Project Domain is the lowest level of Domain and includes Life Cycle Sub-Domains for managing your continuous Delivery Pipeline. This means that a state of your Delivery Pipeline will map to a Project Domain.

Create Environment

An Environment can be created by clicking on the Data Center Menu item, then the Environments tab, and right clicking on the Domain where the Environment is to reside. This pop-up menu includes “New Environment in this Domain.” Select this option to bring up a dialog box, which contains the required fields for defining the New Environment.

Delete Environment

You can delete an Environment by right clicking on the Environment from the tree view and selecting the ‘Delete this Environment’ option.  

Duplicate Environment Names

Duplicates names are restricted. This prevents the User from receiving the duplicate error message even though they cannot see a duplicate name. It would be confusing when a User wants to know which Environment an application is running, or could be deployed against. It is recommended that Environments be named in a specific manner, such as ‘DevEnv-CallCenter,’ and not use the base DevEnv alone.

Editing Environments

The  General Tab on the tree allows you to edit the information by selecting the pencil icon in the right-hand corner of the window.  

Timeline Tab

This tab displays log file entries for the deployment of Applications to the selected Environment. It includes information concerning how many days since the deployment took place, the deployment number, and which User deployed the Application.

Subscribe to a Deployment

The Subscribe link in each entry of the list allows you to receive information about the selected deployment.

Adding Comments to a Timeline

You can add information by clicking on the ‘Comment’ link within a text entry field. These appear in the History column of your subscriber’s home page. There is a field above the list labeled “Say something about this Application” that can have comments placed into it, and files can be attached to the comment as well. Entering text into this field activates the Add Message button. Click on this button to save the comment as a line in the list.  

Adding Files to Your Comments

Clicking on the fingerprint button next to the Add Message button brings up a file explorer that allows files to be selected and attached to the comment. These attachments can later be retrieved by clicking on the fingerprint icon on the far right of the comment, which opens the line in the list to display the name of the file. Click on the file name in the dropdown list. This download into the default Downloads folder of the computer that hosts the browser used to run DeployHub (not on the location hosting DeployHub). The options are standard in every Windows file download interface, including Open, Always Open this Type of File, and Show in folder. Several other lists appear along the bottom of the browser. A small ‘x’ on the far-right side at the bottom can be clicked to make them disappear.

Deployment Details

To view specific details such as the files deployed, the log output, activities executed and other information, click on the deployment number within each line. A window will appear with six tabs:

Tab Name



A list of files that were deployed to the Environment, which includes the Repository’s path of the source file, and the target path where it was placed.


This includes step by step details of the deployment, which includes error messages in red font.


A list of any Actions, Procedures, and Functions that were used during the deployment.

Change Request

(DeployHub Pro only)

The Change Request tab shows enhancement requests and bugs for a selected Application for several popular bug tracking systems, including Bugzilla, GitHub, and Jira.


A synopsis of the deployment, which includes the name of the Application, the date and time of the deployment, and the amount of time the deployment took.


The Reports tab contains two graphs. One displays the time taken for each deployment. Mouse over the dots to see a small translucent box which shows the deployment number and the time taken to deploy in seconds. The second graph is a pie chart which displays the number of successful and failed deployments for each Application onto each End Point within the selected Environment.

Attributes Tab

Values that are stored against an Environment can be used to control deployments. The Name field holds the name of the Value, and the Value field holds the data, which can be either a numeric or text value. It can also be an array of Name/Value pairs associated with a Name. Clicking the plus sign (+) allows you to add a new Attributes. Clicking on the pencil icon allows you to edit an existing Name and its associated Value. Selecting the Attribute from the table and clicking on the “X” in the upper right-hand corner deletes the selected line from the table of Name/Value pairs.

Access Tab

The Access tab allows Users within designated Groups to update the Environment in various ways. To add a Group to one of the access lists, drag and drop the Group from the Available Groups list on the far right into the desired access list. All Users who belong to a Group that appear in one of the Access lists will be granted access to the Environment in the following ways:

NOTE:  DeployHub Team has only two Groups, Administrators and Users.  If you need more granularity in your User Groups, you will need to upgrade to DeployHub Pro.




Allows the User to see the Environment. If the User does not belong to a Group in the View Access list, the Environment will not appear in the tree structure.


Allows the User to change the Environment’s characteristics i.e. Name, Summary, etc.

Create Calendar Entries

Allows Users to control the Calendar for the selected Environment.

NOTE:  Securing Environment Calendars is only available in DeployHub Pro.


Allows Users to deploy Releases and the Applications they contain into the selected Environment.

General Tab

The General Tab displays the basic information that defines an Environment.  Select the pencil icon from the right-hand corner of the window to edit.




The name of the Environment object.


The owner of the Environment, it defaults to the User who created it. The default owner is the User who created the Environment. When editing this field, the Owner Type field is available which includes Owner and Group as choices. Selecting one of these causes the Owner field to display either Users or Groups to choose from.


A short text description of the Environment.


(DeployHub Pro feature)

The default value, "Always Available Unless Denied by Calendar", allows the User to deploy Applications into the Environment unless there is an entry in the Calendar during a specific time (hours, days, weeks) that prevents it from doing so through the use of an added Unavailable section. The other value, "Always Unavailable Unless Denied by Calendar", doesn't allow deployments unless a specific entry in the Calendar overrides it.


The date and time the Environment was created.


The date and time the Environment was last modified.