Ortelius
  • Warning: 0 of 1 Reverse Proxy Online !

Applications

Version Domain Parent Environment Last Deployment to Environment Completed Result domainid appid

Components

Container Application File Database
Version Domain Parent Environment Last Deployment Completed Result domainid compid

Environments

Success/Failed Deployments per Environment Report
Environment Domain domainid envid

Endpoints

Endpoint Domain domainid endpointid

Actions

Action Domain domainid actionid

Func/Procs

DMScript in database Local Script Endpoint Script
DMScript in database Local Script Endpoint Script
Name Domain Type domainid procedureid

Notifiers

HipChat Slack Email SMS
Notifier Domain domainid notifierid

Repositories

File System Http Meister SVN
Repository Domain domainid repositoryid

Data Sources

GitHub Jira Bugzilla LDAP ODBC
Data Source Domain domainid datasourceid

Credentials

Encrypted in Database Private Key
Credential Domain domainid credentialid

Users

User Domain domainid userid

Groups

Group Domain domainid groupid

Types

Type Domain domainid servercomptypeid

Notifiers Templates

Template Notifier templateid
Scorecard Deployment Frequecy Deployment Lag
  • General
  • Package Components
  • Application Service Hierarchy Bundle
  • Delivery Pipeline

Component Owner

Details

Test Connection Results

Access Control

Component Details

Component Domain

Notifier Recipients

  Recipients
  Recipients

Group Membership

  Groups for User
  Groups for User

User Membership

  Users for Group
  Users for Group

Key Value Configuration

Name Value

Access Control

Audit Trail

Event

Readme

Swagger

Vulnerabilities

  Package Version ID Url Summary Component

Software Bill of Materials (SBOM)

Package Version License Url Component

Log History

Deployment Result Date Environment

Key Value Configuration

  Name Value
  Name Value

License

Function/Procedure

Input Parameters

 NameTypeFormatMissingPaddingRequiredPos
 NameTypeFormatMissingPaddingRequiredPos

Command Line Switches

 Name
 Name

Assigned Endpoints

Name Hostname
Name Hostname

Using Variables

When constructing the subject line and message body for a template, you can use Variables. These variables are automatically expanded when the notification is issued.

Variables can be either Object Methods (such as ${application.name}) or Scalar Variables that are set by DeployHub during specific operations (such as $SERVER_STATUS during a periodic server scan).

Object Methods can be used for any object that is available to DeployHub during the operation. For example, you could use ${application.id} to get the internal application id or ${application.domain.name} to get the current domain for the application.

The table below shows which variables are set during specific operations.

Variable NameDescriptionOperation
${application.name}The name of the current applicationAny DeployHub task operating on an Application (such as Deploy, Move, Approve etc)
${environment.name}The name of the target environmentAny DeployHub task operating on an Environment (such as Deploy etc)
${user.name}The name of the invoking userAny DeployHub task.
$DEPLOY_IDThe Deployment ID NumberSet during a Deploy task.
$SERVER_NAMEEndpoint NameThe name of the end point during an automatic periodic scan (AutoPing or AutoMD5). Use this variable in a Ping or MD5 template.
$SERVER_HOSTNAMEEndpoint hostnameThe hostname of the end point during an automatic periodic scan (AutoPing or AutoMD5). Use this variable in a Ping or MD5 template.
$SERVER_STATUSOK or FAILEDThe status of the server during an automatic periodic scan (AutoPing). Use this variable in a Ping template. Note this variable is always OK in an MD5 template since MD5 scans are only performed if the ping check succeeds.
$NAME_RESOLUTIONOK or FAILEDSet during an automatic periodic scan (AutoPing). Reflects the success or failure of resolution of hostname. Use this variable in a Ping template.
$PINGOK or FAILEDSet during an automatic periodic scan (AutoPing). Reflects the success or failure of the ping to the server. Use this variable in a Ping template.
$CONNECTIONOK or FAILEDSet during an automatic periodic scan (AutoPing). Reflects the success or failure of the connection attempt to the server using the associated credentials. Use this variable in a Ping template.
$BASEDIROK or FAILEDSet during an automatic periodic scan (AutoPing). Reflects the success or failure of the attempt to switch to the server's base directory. Use this variable in a Ping template.
$MD5_FILELISTA list of files (one per line)Set during an automatic periodic scan (AutoMD5). Lists all the files whose MD5 checksum differs from that calculated during the last deployment to the server. Use this variable in a MD5 template.
$SRCDOMAINThe name of the Source DomainSet during a Move or Approve task. The name of the Domain the application is being moved from (for a move) or its current domain (for an approve).
$TGTDOMAINThe name of the Target DomainSet during a Move or Approve task. The name of the Domain the application is being moved to or approved for.
$NOTESFree TextSet during a Move, Approve or Request task. The notes that were entered (if any) by the user when the task was run.
$TASKNAMEThe name of the Requested TaskSet during a Request task. The name of the task being requested to be run.
$ERROR_TEXTLast Endpoint ErrorSet during an automatic periodic scan (AutoPing). The last error detected during the connection attempt.

Trends

Current Step Duration

Deployed Components

  Current Version Deployment
  Current Version Deployment

Assigned Environments

  Environment Details
  Environment Details

Deployed Environments

Environment Details

Assigned Applications

Application
Drag the arguments from here onto the command line below to assemble the command. Use the table above to add and configure the switches/arguments.

Change Requests

CR Summary Component Status

Consuming Applications

Endpoints

 EndpointDeployment
 EndpointDeployment

Applications scheduled for this Release

Last Deployment Difference based on Environment:

Providing API End Points

Verb API End Point

Consuming API End Points

Verb API End Point Component

Audit Trail

Event

Access Control

Change Requests

  CR Summary Component Status
  CR Summary Component Status

Dependency Map

Tasks

Approve Verision for move to next pipeline stage Move Version to the next or previous stage in the pipeline Deploy Version to an Environment Request Calendar entry for deployment to an Environment Mannually trigger Action to be executed
  Name

Task Details

Group Access for Task

Available Groups for Task

Task Parameters

Component Selector

  • Global Reports
  • To Do List
  • Audit Trail

Please upgrade to the Pro version in order to create Releases.

Please upgrade to the Pro version in order to create project subfolders.

Sit tight....