Deployments

Deployments are done with applications. Running a deployment is straightforward: you run a deployment-type process that is defined for an application in one of its environments.

(Application processes can do things other than deploying, such as rolling-back or uninstalling components.) To run an application process, click Request Process on the application Environment pane (Application > selected_application > Environment).

Figure 1. Request Process actions

Follow these steps to run an application:

  1. In the IBM® UrbanCode Deploy web application, display the Application tab.
  2. Click the name of the application.
  3. Use the Request Process action for the environment where you want the deployment to be run. The Run Process dialog is displayed.

    In the illustration above, the application has two environments. Click the Run Process link for the environment you want to use.

    Figure 2. Run Process dialog
  4. If you want to use a snapshot, select it from the Snapshot list. If you select a snapshot, the deployment automatically uses the component versions that are defined for the snapshot. For information about snapshots, see Snapshots.
  5. If you did not select a snapshot, select a component version from the Version list-box. If more than one component is mapped to the application, each one is listed separately. Version options are described in the following table:
    Table 1. Version options
    Version Option Description
    None No version for this component. Useful when you run multi-component deployments or tests.
    Specific Version You can select any version in Codestation.
    Latest Version Automatically uses the most recently imported version.
    Latest With Status All versions with the selected status, from oldest to newest. Using this option can affect multiple versions, for an incremental component. Default values include Latest, Passed Test, Archived.
    All With Status All component versions with the selected status are deployed. Default values include Latest, Passed Test, Archived.
    All in Environment Deploys all versions (in order of deployment) with the specified inventory status in the current environment. This option is useful to run an operational process for whatever is already in the environment. Default values include Active, Staged.
    All in Environment (Reversed) All component versions that are already deployed in the environment with the selected inventory status are deployed in reverse order.
  6. Use the Only Changed Version check box to ensure that only changed versions are deployed (it is checked by default). If checked, no previously deployed versions are deployed. If, for example, you check the box and select a specific version that was already deployed, the version is not redeployed. Clear the box if you want to deploy a version regardless of whether it was already deployed (if the inventory is out of date, for instance).
  7. Select the process to run from the Process list. All processes for the application are listed.
  8. If you want to run the process later, click the Schedule Deployment? check box (it is cleared by default). If checked, fields are shown that specify the date and time when the process runs. You can also make the process run on a recurring basis.
  9. When finished, click Submit to start the process. An application process starts immediately unless scheduled for a later time.

When a process starts, use the Application Process Request pane to review the deployment status. This pane is also used if the process requires approvals.

Figure 3. Application Process Request pane

After a process finishes, click the Details action to display the Deployment of Component pane, which can be used to review the deployment details.

The actions available for this pane enable you to review the deployment output log, error log, and input/output parameters.


Feedback