Welcome
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.
Build
Build offers the capability to build applications, manage continuous integration workflows, and store build artifacts.
Administering
Users with the correct permissions can configure security, create users, configure integrations, and create notifications and announcements among other things.
Server management
Use server settings to manage your server other system-related settings.
Adding a cold standby server
Adding a standby server provides a backup server for disaster recovery in case the main server for Build is lost. A cold standby server is not turned on until needed. The environment must be configured to route network traffic to the standby server after a failure of the primary server.

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 and Measure 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.
  - System requirements
  - Overview of Build
    Build is a continuous integration and build-management system.
  - Tutorials
    This section contains tutorials for users of all experience levels. If you are new to Build, this tutorials introduces the most-used product features in an easy-to-follow way. You do not need additional resources to complete the tutorial.
  - Administering
    Users with the correct permissions can configure security, create users, configure integrations, and create notifications and announcements among other things.
    - Configuring an external agent for Build in DevOps Loop
      You can configure an external Build agent to connect with DevOps Loop installed on Kubernetes (K8s), Azure Kubernetes Service (AKS), IBM Kubernetes Service (IKS), or OpenShift Container Platform (OCP).
    - Integrating Build resources with existing loop and teamspaces
      You can integrate the previously created Build resources, including teams, mappings, and agent pools to an existing teamspace and loop after you upgrade from DevOps Loop 1.0.2 to 1.0.3 or later.
    - Integrations
      When you configure integrations, you allow Build to use and manage the objects and artifacts that are produced in external tools such as HCL DevOps Deploy (Deploy).
    - Managing scripts
      The script library provides numerous scripts for you to use and modify.
    - User notifications
      Build can send information about build results to selected users by email, instant messaging, and other methods.
    - Security
      Build provides a flexible team-based, and role-based security model that maps to your organizational structure.
    - Project support
      Projects represent items that can be built individually for release or distribution.
    - Server management
      Use server settings to manage your server other system-related settings.
      - Creating announcements
        Announcements are messages that are displayed on the Build dashboard for all users.
      - Creating system properties
        System properties can set system-wide values for processes and projects.
      - Creating proxy servers
        Use a proxy server if you need to access servers or repositories, such as Maven, that are on external networks.
      - Server settings
        Use server settings to configure server-related features, such as displaying graphs on users' dashboards.
      - Adding a cold standby server
        Adding a standby server provides a backup server for disaster recovery in case the main server for Build is lost. A cold standby server is not turned on until needed. The environment must be configured to route network traffic to the standby server after a failure of the primary server.
    - Agents
      Agents are light-weight processes that are installed on hosts and communicate with the Build server.
    - Creating scripts to automate administrative tasks
      The Build Client facilitates writing scripts that interact with various REST endpoints in Build to automate tasks such as creating templates, assembling projects, running builds, and various other administrative tasks.
    - Accessing development tools
      Use the Tools window to access the Build development tools.
    - Installing plug-ins
      You install plug-ins by downloading the installation files and loading them into Build.
  - Creating and Managing Projects
    Projects run builds, manage dependencies with third-party tools, and can be used for administrative, operational, and system maintenance.
  - Build pipelines
    A build pipeline defines the automated process that transforms source code into deployable artifacts. It specifies the steps required to compile, test, validate, scan, and package the code.
  - Creating Jobs and Processes
    Jobs are the core building blocks of Build. Process definitions assemble jobs into the basic unit of automation. A process definition determines how, when, and where jobs run.
  - Managing Project Templates
    Project templates are reusable plans that map build processes.
  - Monitoring and Reporting
    With the monitoring tools you can review current and historical activity and save your filter conditions for future use. You can create charts and reports from most database tables.
  - Extending Product Functions
    You can create your own plug-ins to extend the product’s capabilities.
- 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.
- 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, 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.

Adding a cold standby server

Adding a standby server provides a backup server for disaster recovery in case the main server for Build is lost. A cold standby server is not turned on until needed. The environment must be configured to route network traffic to the standby server after a failure of the primary server.

Before you begin

Make sure that the server is connected to a license server with available licenses.
Ensure that you have the required security rules to get from your various endpoints to both the primary server and to the standby server.

About this task

At any given time, only one of the servers is active and connected to agents, the database, and network file systems. If the primary server encounters any issues and becomes nonoperational, then the standby server can be brought online and incoming network traffic can be directed to it instead of the primary server.

Both the primary and standby server must use the same database. The following directories and files must be moved to a network storage location that is accessible by both servers:

server/var			
server/plugin
server/patches
server/opt/tomcat/webapps
server/opt/tomcat/work 	
server/conf/server.keystore
server/conf/server/base.xml
server/conf/server/ehcache.xml
server/conf/server/java.security
server/conf/server/hibernate.properties
server/conf/server/log4j.properties
server/conf/server/spy.properties
server/conf/server/rsa_api.properties
server/conf/server/upgrade.properties

All files and directories in the server/opt/tomcat/work directory should be deleted whenever a new patch is applied to the server.

Procedure

Install the standby server in a separate location and connect it to the same database as the primary server.

Specify the database that the production server is using when prompted for database information.

Note:
Do not start the server.
Set up the environment to stop the primary server, start the standby server, and direct traffic to it in the case of a failure with the primary server.
If a load balancer is used to switch to the standby sever, set the install.server.external.web.url property for both server instances to the URL of the load balancer.