Welcome
Administration
This section provides information on administration, installation, configuration, and integrations and teamspace management.
Configuration of external databases for the capabilities in DevOps Loop
DevOps Loop capabilities use databases to store configuration data, execution results, and operational information. In the default configuration, some capabilities deploy internal databases as part of the Helm installation. However, you can configure the capabilities to use external databases that are managed outside the Kubernetes cluster.
Configuring an external database for Build
You can configure Build to use the same external MySQL database that is used by Deploy. When using an external database, the Build Helm chart must be configured to connect to the existing MySQL instance instead of creating a database inside the Kubernetes cluster.

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.
- Configuration of external databases for the capabilities in DevOps Loop
  DevOps Loop capabilities use databases to store configuration data, execution results, and operational information. In the default configuration, some capabilities deploy internal databases as part of the Helm installation. However, you can configure the capabilities to use external databases that are managed outside the Kubernetes cluster.
  - Configuring an external database for Plan and Control
    You can configure an external PostgreSQL database for the Plan capability in DevOps Loop and provide the database connection details in the Helm chart so that Plan connects to the external database instead of using the default PostgreSQL service included with the chart.
  - Configuring an external database for Deploy
    You can configure an external database for the Deploy capability in DevOps Loop and provide the database connection details in the Helm chart so that Deploy connects to the external database instead of creating one within the cluster.
  - Configuring an external database for Build
    You can configure Build to use the same external MySQL database that is used by Deploy. When using an external database, the Build Helm chart must be configured to connect to the existing MySQL instance instead of creating a database inside the Kubernetes cluster.
  - Configuring an external database for Test
    You can configure an external PostgreSQL database for the Test capability in DevOps Loop and provide the database connection details in the Helm chart so that Test connects to the external database instead of using the PostgreSQL instance that is installed in the cluster by default.
  - Configuring an external database for Measure and Release
    You can configure Measure and Release to use an external MongoDB database by creating a Kubernetes secret to store the database connection URL and updating the Helm chart to reference this secret.
  - Configuring external access to the Plan PostgreSQL database
    You can configure external PostgreSQL access during installation by using a Helm upgrade.
- Installation of DevOps Loop
  To get started working with HCL DevOps Loop, you must first install DevOps Loop.
- License management and user administration
  After you install HCL DevOps Loop, you must consider how the platform manages licenses, users, and authentication.
- Backup and restoration of DevOps Loop
  You must back up HCL DevOps Loop data before you uninstall the current version of DevOps Loop. You must back up the data to avoid data loss or inaccessibility.
- Private CA and self-signed certificate support
  A private Certificate Authority (CA) is an organization-specific service that issues and manages digital certificates for use within an enterprise’s private network. These certificates secure communication between internal applications and services.
- Upgrading DevOps Loop
  After you complete certain backup and pre-upgrade steps, you can upgrade DevOps Loop to a newer version by using Helm.
- Integrations in DevOps Loop
  DevOps Loop provides a set of integrations to extend the platform’s capabilities and connect your loops to external systems and intelligent tools. These integrations enable you to automate tasks, enhance productivity, and interact with loop resources from outside the DevOps Loop interface.
- DevOps Loop MCP server
  The DevOps Loop Model Context Protocol (MCP) server provides a standardized interface so that external MCP clients can interact with DevOps Loop and perform supported operations.
- Teamspace management
  A teamspace in HCL DevOps Loop is a secure, dedicated environment designed for multiple teams to work independently within a single shared DevOps Loop installation.
- Uninstalling DevOps Loop
  You can safely uninstall DevOps Loop from your environment, ensuring that all resources and data are properly removed.
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 and Measure to manage every stage of the software development lifecycle within a connected, continuous loop.
Loop Genie overview - Tech Preview
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.
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.

Configuring an external database for Build

You can configure Build to use the same external MySQL database that is used by Deploy. When using an external database, the Build Helm chart must be configured to connect to the existing MySQL instance instead of creating a database inside the Kubernetes cluster.

Before you begin

You must have completed the following tasks:

Ensured that the external MySQL database used by Deploy is available and accessible from the Kubernetes cluster.
Ensured that the following information is available:
- MySQL host name or IP address
- MYSQL port
- Database name
- Database user name
- Database password
Ensured that the database user has permission to access the required database.
Ensured that the Kubernetes cluster is connected to the MySQL server.
Esnured that a Kubernetes secret containing the database password exists in the deployment namespace.

Procedure

Add variables for the external MySQL database in the installation script:
```
MYSQL_HOST=<mysql-host>
MYSQL_PORT=3306
DATABASE_NAME=<database-name>
DATABASE_USER=<database-user>
BUILD_DB_SECRET=build-secret
```
These variables define the connection details for the external MySQL database used by the Build.
Create a Kubernetes secret that contains the database password by running the following command:
```
BUILD_DB_PASSWORD=<DATABASE_PASSWORD>
kubectl create secret generic build-secret -n devops-loop --from-literal=dbpassword="$BUILD_DB_PASSWORD"
```
⚠️ Important: The BUILD_DB_PASSWORD must match the password assigned to the MySQL user.

Add the following Helm values to the HELM_OPTIONS section of the installation script. These parameters configure the Build Helm chart to use the external database.

--set hcl-devops-build.externalDB.enabled=true \
--set hcl-devops-build.externalDB.hostname=<MYSQL_HOST> \
--set hcl-devops-build.externalDB.port=<MYSQL_PORT> \
--set hcl-devops-build.externalDB.database=<DATABASE_NAME> \
--set hcl-devops-build.externalDB.user=<DATABASE_USER> \
--set hcl-devops-build.secret.name=build-secret

Results

After you run the installation script, DevOps Loop is installed and the Build capability connects to the external MySQL database by using the credentials stored in the Kubernetes secret.

What to do next

You must install DevOps Loop to apply the configuration. See Installation of DevOps Loop.