HCL DevOps Loop provides an integrated suite of capabilities such as Plan, Code, Control, Build, Test, Release, Deploy and Measure to manage every stage of the software development lifecycle within a connected, continuous loop.
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 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.
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).
You can create, delete, and modify the contents of the resource tree.
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.
This document includes information about hardware and software requirements for HCL DevOps Loop.
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.
This section provides information on administration, installation, configuration, and integrations and teamspace management.
A loop is a workflow that connects DevOps activities of your team from planning and development through build, deployment, testing, and release phases.
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 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 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 offers the capability to build applications, manage continuous integration workflows, and store build artifacts.
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 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.
Quickly become productive with HCL DevOps Deploy (Deploy).
You can install and connect an external Deploy agent to a DevOps Loop instance running on Kubernetes (K8s), and IBM Kubernetes Service (IKS).
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
HCL DevOps Deploy (Deploy) uses a flexible team-based and role-based security model that maps to your organizational structure.
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 represent deployable items along with user-defined processes that operate on them, usually by deploying them.
Resources associate agents with components and, after they are mapped to an application environment, provide deployment targets.
Resource groups organize resources into logical groupings.
Agent-type and agent pool-type resources represent the computers where components are deployed.
Component-type resources represent the components that are deployed to target environments.
You can find agents that are not associated with a resource and add them to a resource group.
Resource tree structures in the Resources Tree page can be configured by moving and copying the resources using the drag and drop feature.
When you no longer require the resources, you can remove them from the Resource Tree page and choose to delete them permanently.
When you no longer require the resources permanently, you can delete the resources from the Recycle Bin by setting up time and duration for the cleanup.
When needed, you can choose to restore the resources to their original locations in the Resource Tree after you delete them. When restored, the resources are restored as a child resource of the original parent resource. If the parent is moved, the resource is restored to the parent's new location. However, after resources are deleted from the Recycle Bin, they cannot be restored.
You can compare the contents of a resource group to another group or a resource template and then apply changes to the group or template.
You can add the contents of a resource template to the top-level resource group.
You can add the structure from a resource template to a new group within an existing resource group.
Use the WebSphere® Application Server - Deploy plug-in to import information about an IBM® WebSphere Application Server system into a collection of resources. Typically, importing information by using the plug-in takes less time than manually creating resources to match the IBM WebSphere Application Server.
With the WebSphere® Portal plug-in, you can discover resources for a portal cell and use plug-in steps to deploy artifacts.
You can define default user impersonation credentials for a resource.
A resource template is a model for a group of resources. The template contains a hierarchy of resources, groups, and agent prototypes that is a starting point for creating new resources.
An agent is a lightweight process that runs on a deployment-target host and communicates with the HCL DevOps Deploy (Deploy) server.
Agent relays coordinate communication between agents and the HCL DevOps Deploy (Deploy) server. Agent relays improve the performance of communication between the server and agents. Relays also allow agents to communicate through firewalls.
Applications are responsible for bringing together all the components that must be deployed together.
An environment is a user-defined collection of resources that hosts an application.
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, like component processes, are created with the process editor. You use application processes to deploy or to roll back components.
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.
Allows you to run application processes in multiple environments and promote versions through a set of stages.
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.
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.
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.
You use different inventories to track installed components and properties in HCL DevOps Deploy (Deploy) elements.
Processes are automated tasks that run on agents.
Create and apply statuses to track component inventory states or to track component versions in environments and resources.
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.
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.
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.
Learn how to deploy applications in HCL DevOps Deploy (Deploy).
Provides several different deployment and security reports.
Learn how to extend the function of HCL DevOps Deploy (Deploy).
Learn how to troubleshoot some common issues with HCL DevOps Deploy (Deploy).
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 is an AI-powered, multi-agent assistant integrated into DevOps Loop. It provides a unified conversational interface to perform tasks and retrieve information across multiple DevOps Loop capabilities.
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.
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.
This document provides information about copyright, trademarks, terms and conditions for the product documentation.