Welcome
Administering
This guide describes how to install HCL DevOps Velocity (Velocity). After you install Velocity, you can perform administrative tasks such as license configuration, upgrading, migrating, managing access permissions and security. This guide is intended for system administrators.
Plugin multiplexing
Plugin multiplexing lets integrations that use the same plugin type and version share pods in Velocity.

Release Notes
This document includes information about the new features introduced, defects fixed, and known issues identified in this version of HCL DevOps Velocity (Velocity). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System Requirements
This document contains information about hardware and software requirements for HCL DevOps Velocity (Velocity).
Getting Started
This document provides an overview of HCL DevOps Velocity (Velocity).
High-Level Overview
Use HCL DevOps Velocity (Velocity) to automate your release lifecycle and manage your DevOps value streams.
Tutorials
Learn how to complete frequently-used tasks such as creating value streams.
Managing licenses
Configure your license or apply a trial key.
Administering
This guide describes how to install HCL DevOps Velocity (Velocity). After you install Velocity, you can perform administrative tasks such as license configuration, upgrading, migrating, managing access permissions and security. This guide is intended for system administrators.
- Installing DevOps Velocity
  To get started with HCL DevOps Velocity (Velocity), you must install it on any one of the container platforms. You can find information about the selection of a container platform, installation methods, and procedure for installing Velocity.
- Installing DevOps Velocity plugins on air-gapped networks
  HCL DevOps Velocity (Velocity) plugin installations on air-gapped networks.
- Uninstalling DevOps Velocity
  You can uninstall HCL DevOps Velocity (Velocity) by stopping the server and removing the product containers.
- Configuring trusted certificates in DevOps Velocity
  The default configuration in Velocity accepts connections with self-signed CA certificates. You can configure Velocity to restrict self-signed CA certificates and allow only a predefined set of trusted CA certificates.
- Plugin multiplexing
  Plugin multiplexing lets integrations that use the same plugin type and version share pods in Velocity.
  - Enabling plugin multiplexing
    You must enable plugin multiplexing to allow multiple integrations that use the same plugin type and version to share a pod, which can reduce the number of pods required for plugin executions. By default, plugin multiplexing is enabled for the DevOps Plan, DevOps Deploy, DevOps Build, and DevOps Control plugins. You can update the list of multiplexed plugin types in the values.yaml file.
  - Changing the multiplexed plugin limit
    You can optimize resource utilization and adjust pod capacity by updating the values.yaml file to change the maximum number of integrations of the same plugin type and version that can share a single pod.
- Upgrading DevOps Velocity
  You can find information about upgrading of HCL DevOps Velocity (Velocity).
- Migrating DevOps Velocity
  You can find information about migration of HCL DevOps Velocity (Velocity) to another container orchestration.
- Configuring DevOps Velocity
  A default Velocity administrator ID is included as part of Velocity. It is used to install and complete initial configuration tasks.
- DevOps Velocity MCP Server - Tech Preview
  A Model Context Protocol (MCP) server provides a structured way for GenAI clients to access tools, data, and actions through a consistent, secure interface. When you connect a GenAI client that supports MCP to the Velocity MCP server, you can use natural-language requests to retrieve information from your Velocity.
Managing Value Streams
A value stream represents the objects and activities that you employ to deliver customer value, from initial concept to final delivered project.
Data Insights
The Insights feature provides DevOps metrics for your project data.
Analytics Dashboards
Analytics creates team-specific dashboards that generate charts for each activity of the product development. HCL DevOps Velocity (Velocity) creates dashboards automatically while you create a team.
Releasing Software
A release is a repeatable plan that is used to drive deployments.
Extending Product Functions
Learn how to extend the function of VelocityVelocity
How to
The topics in this section describe how to work with Velocity features. Tutorials and workbooks are available for users of all experience levels.
Troubleshooting
Before you contacting support, gather background information and perform tasks that will assist in solving the problem. It helps to be as specific as possible and include all relevant information.
Notices for DevOps Velocity
This document provides information about copyright, trademarks, terms and conditions for the product documentation.
DevOps Velocity GDPR statement
General Data Protection Regulation (GDPR) has been adopted by the European Union (EU) and applies from May 25, 2018.
Glossary

Plugin multiplexing

Plugin multiplexing lets integrations that use the same plugin type and version share pods in Velocity.

Plugin multiplexing is enabled by default for the DevOps Plan, DevOps Deploy, DevOps Build, and DevOps Control plugins. You can configure the list of multiplexed plugins and change the maximum number of integrations that can share a pod.

Plugin multiplexing is configured through the values.yaml file. The multiplexedPlugins setting identifies the plugin types that support multiplexed execution, allowing multiple event executions to share the same pod. The multiplexedPluginLimit setting defines the maximum number of event executions that can share a pod for a given plugin type and version. Together, these settings determine which plugins use multiplexed mode and the execution capacity available within each shared pod.

When multiplexing is enabled, Velocity groups event executions from integrations that use the same plugin type and version. Each group of matching event executions runs in a shared pod, up to the limit specified by multiplexedPluginLimit.

Grouping events across integrations

Suppose 10 integrations use the DevOps Build plugin with version 5.2.0, and each integration has three events. Velocity groups the matching event executions across the 10 integrations. As a result, the executions for the first event can share a pod, the executions for the second event can share a pod, and the executions for the third event can share a pod, subject to the multiplexedPluginLimit setting.