Welcome
Capabilities of DevOps Loop
HCL DevOps Loop provides an integrated suite of capabilities such as Plan, Code, Control, Build, Test, Release, Deploy, Measure and Harbor (if enabled) to manage every stage of the software development lifecycle within a connected, continuous loop.
Deploy
Deploy standardizes and simplifies the rollout of software components across environments within the DevOps Loop. Its release automation tools improve deployment speed and reliability, providing visibility into multi-tiered deployments and orchestrating complex processes across environments and approval gates.
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) 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.
Component processes
A component process is a series of user-defined steps that operate on a component's artifacts.
Exporting specific component processes
You can export specific component processes to save and share deployment configurations for reuse across applications or environments.

Release Notes
This document includes information about the features introduced, a product overview, and installation instructions, as well as contact information of HCL Customer Support for this version of HCL DevOps Loop.
System Requirements
This document includes information about hardware and software requirements for HCL DevOps Loop.
Getting Started
HCL DevOps Loop is a platform designed to support the full DevOps lifecycle. The Getting Started section introduces key concepts and walks through the initial steps to help new users begin working with the platform.
Administration
This section provides information on administration, installation, configuration, and integrations and teamspace management.
Working with Loops
A loop is a workflow that connects DevOps activities of your team from planning and development through build, deployment, testing, and release phases.
Capabilities of DevOps Loop
HCL DevOps Loop provides an integrated suite of capabilities such as Plan, Code, Control, Build, Test, Release, Deploy, Measure and Harbor (if enabled) to manage every stage of the software development lifecycle within a connected, continuous loop.
- Plan
  Plan is a change management software application within the DevOps Loop that supports seamless ticket creation, tracking, and comprehensive issue management. With customizable workflow automation, it helps teams to streamline and adapt processes to meet their unique business requirements while preparing work for the next stages of the loop.
- Code
  Code is a cloud-based browser IDE in a dev container that is part of HCL DevOps Loop, allowing developers to write, compile, build, and debug code directly in the browser without requiring local setup.
- Control
  Control manages source code within the DevOps Loop using GitHub compatible APIs that integrate with existing developer tools, workflows, and automation. It supports version management, collaboration, and code governance as development progresses.
- Build
  Build offers the capability to build applications, manage continuous integration workflows, and store build artifacts.
- Test
  The Test capability in DevOps Loop is powered by the DevOps Test application. Test centralizes test data, environments, test runs, and reports in a single web based interface within the DevOps Loop. It streamlines test management, execution, and tracking, providing greater efficiency and visibility to ensure quality throughout the loop.
- Release
  Release standardizes and automates the software release lifecycle with the DevOps Loop, moving applications smoothly from preproduction to production. It provides predictable scheduling, integrates changes from planning tools, and gives stakeholders clear visibility into plans and milestones.
- Deploy
  Deploy standardizes and simplifies the rollout of software components across environments within the DevOps Loop. Its release automation tools improve deployment speed and reliability, providing visibility into multi-tiered deployments and orchestrating complex processes across environments and approval gates.
  - Getting Started
    Quickly become productive with HCL DevOps Deploy (Deploy).
  - Installing an external agent for Deploy in DevOps Loop
    You can install and connect an external Deploy agent to a DevOps Loop instance running on Kubernetes (K8s), and IBM Kubernetes Service (IKS).
  - Integrating
    HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
  - Administering
    Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
  - Managing Security
    HCL DevOps Deploy (Deploy) uses a flexible team-based and role-based security model that maps to your organizational structure.
  - Modeling Software Deployment
    Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
    - Dashboard
      The Dashboard is a live page that gives you real-time insights into the status of your deployments and agents through graphs and charts.
    - Components
      Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
      - Creating components
        A component consists of artifacts of a single source type and one or more processes. Component creation is the same for all source types, however; the content can be different.
      - Component processes
        A component process is a series of user-defined steps that operate on a component's artifacts.
        Importing specific component processes
        Component processes define the steps required to deploy, configure, or update a specific component. You can import specific component processes to reuse a standardized deployment across multiple applications or environments without recreating a process each time.
        Exporting specific component processes
        You can export specific component processes to save and share deployment configurations for reuse across applications or environments.
      - Component versions
        Each time a component's artifacts are imported into the repository, including the first time, a separate version is stored in CodeStation. Versions can be assigned automatically by HCL DevOps Deploy (Deploy), applied manually, or come from a build server.
      - Component properties
        Components can have several types of properties. The server keeps track of changes to component properties as property versions.
      - Creating component manual tasks
        A component manual task interrupts a component process until manual intervention is done. To create a component manual task, add a manual step to a component process, and select a notification template.
      - Component templates
        With a component template, you can save and reuse component processes and properties and create components from them; template-based components inherit the template's properties and process.
      - Component change logs
        Change logs provide information about modifications to components.
      - Deleting components
        When a component is deleted, it cannot be activated later.
    - 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 DevOps Deploy (Deploy).
    - 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.
    - 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.
    - 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 DevOps Deploy (Deploy) 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 a webhook, 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.
  - Deploying
    Learn how to deploy applications in HCL DevOps Deploy (Deploy).
  - Reporting
    Provides several different deployment and security reports.
  - Extending Product Function
    Learn how to extend the function of HCL DevOps Deploy (Deploy).
  - Troubleshooting and Support
    Learn how to troubleshoot some common issues with HCL DevOps Deploy (Deploy).
- Measure
  Measure provides end-to-end visibility into the DevOps Loop, giving teams to track how value is created throughout the work flow. It consolidates testing, security, and performance metrics to identify bottlenecks, team issues, and opportunities for improvement while strengthening governance across the organization.
Loop Genie overview - Tech Preview
Loop Genie is an AI-powered assistant integrated into DevOps Loop. It provides a unified conversational interface for retrieving information and performing actions across multiple DevOps Loop capabilities.
Troubleshooting
Offline Documentation (PDF)
You can access the following link to view or download the release notes, system requirements, and user documentation for DevOps Loop in a Portable Document Format (PDF) file.
Security Considerations
This document describes the actions that you can take to ensure that your installation is secure, customize your security settings, and set up user access controls in HCL DevOps Loop.
Notices
This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Exporting specific component processes

You can export specific component processes to save and share deployment configurations for reuse across applications or environments.

Before you begin

You must have identified the component processes that are to be exported.

About this task

Exporting component processes creates JSON or YAML file (file extension), that contains processes for the components. For more information about JSON, see http://www.json.org/. You can export one or more specific component processes as YAML or JSON files.

Note:

When you export components, applications, processes, or templates, and then import them on a different computer, the same versions of the same plug-ins must be installed on both computers.

Procedure

Log in to Deploy.
Click Components.
The Components page is displayed.
Click the component from which you want to export the specific process.
Click Processes tab.
The list of associated process with the selected component is displayed.
Export the processes using any of the following methods:.
- To export processes in bulk:
  1. Select the processes to be exported.
  2. Click Bulk Actions.
  3. Select Export to JSON or Export to YAML.
- To export a latest promoted process:
  1. Click the menu option of the process to be exported.
  2. Select Export to JSON or Export to YAML.
- To export a draft process:
  1. Open a process in the process designer.
  2. Select a draft version, if required.
  3. Click Export > Export to JSON or Export > Export to YAML.

Results

You have exported the specific component processes to your local system in the selected file format.

What to do next

After exporting the specified component processes, you can import them into other instances for future use.