Home
Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Application pipelines
Allows you to run application processes in multiple environments and promote versions through a set of stages.
Executing pipelines
After you define a pipeline, you can execute it using the Web UI.

Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
- Components
  Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
- Resources
  A resource is a logical deployment target that typically resolves to an agent and a user-defined construct that is based on the architectural model of HCL Launch.
- Applications
  Applications are responsible for bringing together all the components that must be deployed together.
- Application environments
  An environment is a user-defined collection of resources that hosts an application.
- Application templates
  With an application template, you can save and reuse a collection of resources, environments, processes, and tagged components or component templates to create a standardized application.
- Application processes
  Application processes, like component processes, are created with the process editor. You use application processes to deploy or to roll back components.
- Application blueprints
  An application blueprint maps application components to a resource template. When you create an environment or provision one from the cloud, you can use the blueprint as a model.
- Application pipelines
  Allows you to run application processes in multiple environments and promote versions through a set of stages.
  - Managing pipelines
    You manage pipelines by defining, editing, deleting, and tracking the execution history of pipelines.
  - Executing pipelines
    After you define a pipeline, you can execute it using the Web UI.
- Snapshots
  A snapshot is a collection of specific versions of components and processes. Typically, a snapshot represents a set of component versions that are known to work together. In most cases, snapshots include all of the components in an application.
- Creating manual application tasks
  A manual application task interrupts an application process until manual intervention is done. To create a manual task, add a manual step to an application process and select a notification template.
- Approval process
  You can add approval requirements to deployments. Deployments with approvals cannot be completed until all approvers respond. Approvers can respond to requests on the Work Items tab, or by email.
- Inventories
  You use different inventories to track installed components and properties in HCL Launch elements.
- Processes
  Processes are automated tasks that run on agents.
- Statuses
  Create and apply statuses to track component inventory states or to track component versions in environments and resources.
- Properties
  Properties are variables that store information about many different elements, including components, environments, processes, and applications. You can also set global properties for the system.
- Tags
  A tag is a user-defined, shared, short label that you use to classify, view, and conduct operations on objects such as applications, components, agents, and resources.
- Webhooks
  Using the webhooks, you can send text-based responses to users in messaging platform such as MS Teams and Slack when a specific event occurs during deployment process.
- Secret Stores
  Allows you to retrieve credentials of individual servers from the Vault and authenticates a plug-in step in the deployment process.

Executing pipelines

After you define a pipeline, you can execute it using the Web UI.

Before you begin

Before executing a pipeline, understand how runtime objects such as stage and blocks act in a pipeline exection:

Pipeline execution:
- Stages are executed sequentially.
- The next stage starts only when the previous stage is completed successfully.
- A pipeline completes successfully only when all stages are completed successfully.
Stage execution:
- Each block in a stage is executed concurrently.
- A stage completes successfully only when all blocks complete successfully.

Block execution:
- Each process is executed sequentially.
- The next process starts only when the previous process is completed successfully.
- A block completes successfully only when all processes are completed successfully.

About this task

Execute a pipeline from the Application page as follows:

Procedure

Go to application_name > Pipelines > Pipeline Execution or click on play button next to a pipeline.
Select a snapshot or choose a component version that you want to deploy.
Click on Submit.
The pipeline executes and shows the runtime objects that further represents the execution status. An execution have statuses such as Not Started, Starting, Running, Canceling, Completed, and Canceled.

Results

The historical record of completed pipelines or any running pipeline execution is listed in the History tab. A pipeline execution can be tracked for the details such as Status, Started date and time, Completed date and time, Payload, and Initiated By.