Welcome to the HCL™ Accelerate version 3.1.x documentation, where you can find information about how to install, maintain, and use HCL Accelerate.
This document contains information about what's new, bug fixes, known issues, and upgrade notes.
This document provides an overview of HCL™ Accelerate.
This document contains information about hardware and software requirements for HCL™ Accelerate.
Use HCL™ Accelerate to automate your release lifecycle and manage your DevOps value streams.
Learn how to complete frequently-used tasks such as creating value streams.
All production instances of HCL™ Accelerate must be installed on a Kubernetes platform. As a part of this migration, the instance of MongoDB need to be re-installed in a Kubernetes-accessible location. To migrate your MongoDB database, follow the steps below. After completion of these steps, follow the Kubernetes installation procedure to complete the installation of HCL Accelerate.
Starting with HCL™ Accelerate version 3.1.0, OpenShift installation via templates is no longer supported. It is highly recommended to migrate OpenShift template installation of HCL Accelerate to Kubernetes Helm charts on your next upgrade. After the successful migration, follow the Kubernetes upgrade directions.
A default HCL™ Accelerate administrator ID is included as part of HCL Accelerate. It is used to install and complete initial configuration tasks.
A value stream represents the objects and activities that you employ to deliver customer value, from initial concept to final delivered project.
The Insights feature provides DevOps metrics for your project data.
A release is a repeatable plan that is used to drive deployments.
Learn how to extend the function of HCL™ Accelerate
The topics in this section describe how to work with HCL™ Accelerate features. Tutorials and workbooks are available for users of all experience levels.
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.
You can migrate from one container to another container orchestration.
