Welcome
Releasing Software
A release is a repeatable plan that is used to drive deployments.
Deployment plans
A deployment plan is a container for tasks. Tasks define the activities that your team runs to complete a software deployment.
Copying deployment plans
You can duplicate deployment plans by copying them.

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.
Learning
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.
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.
Developing 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.
- Managing a release
  Use the release details page to view details about a specific release.
- Managing releases
  Release management is the process of planning, scheduling, and controlling software deliveries.
- Creating releases
- Archiving releases
  You can archive a release to remove it from the list of releases.
- Events and tags
  An event represents a release-related activity that you manage with the calendar. A tag is a label that you can add to a release or an event. You can use tags to filter the Activities list on the Releases page. Tags do not appear on the calendar.
- Restoring archived releases, plans, and templates
  You can restore archived releases, deployment plans, and templates.
- Deployment plans
  A deployment plan is a container for tasks. Tasks define the activities that your team runs to complete a software deployment.
  - Managing deployment plans
    You can change existing deployment plans and view current status from the Deployment Plan details page.
  - Creating deployment plans
    You can start with a blank plan that has no defined tasks, copy an existing plan, or start with a plan template. You can also auto-create them by assigning applications to pipelines. When you copy a plan or use a template, many tasks are already defined.
  - Importing tasks into deployment plans
    You can import tasks that are defined in comma-separated values (CSV) files into a deployment plan.
  - Copying deployment plans
    You can duplicate deployment plans by copying them.
  - Managing deployment plan templates
    You can convert deployment plans to create deployment plan templates.
  - Archiving deployment plans
    You can remove deployment plans from releases by archiving them.
- Running deployments
  Complete deployments by resolving the tasks in a deployment plan.
- Tasks
  A task represents a business-meaningful activity that is associated with a software deployment. Each task is defined on a separate row in a deployment plan. During a deployment, you run tasks defined in the deployment plan to complete the deployment.
- Properties
  A deployment plan can contain user-defined properties. Properties values can be defined at design- or run-time.
Extending Product Functions
Learn how to extend the function of HCL DevOps Velocity (Velocity)
How to
The topics in this section describe how to work with HCL DevOps Velocity (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

Copying deployment plans

You can duplicate deployment plans by copying them.

About this task

The status of a copied or promoted plan is `draft` even if the original plan has a status of `done` or `in progress`.

Procedure

Optional: To copy a plan, click the overflow icon () and select Copy plan from the drop-down on the Releases details page. When you copy a plan, a new plan with the name "Copy of `plan_name`" is inserted into the Releases details page. The copied plan contains all the tasks that are defined in the original plan. If HCL DevOps Deploy (Deploy) tasks are in the plan, the applications, versions, and environments that are selected in the original are also selected in the copied plan. Applications, versions, and environments are displayed on the **Versions** tab on the Deployment Plan Detail page.
Optional: To create a template from a plan, click the overflow icon () and select Copy as template from the drop-down on the Releases details page. When you copy a plan as a template, a new plan with the name "Copy of `plan_name`" is inserted into the Templates page. The copied plan contains all the tasks that are defined in the original plan. If Deploy tasks are in the plan, the applications, versions, and environments that are selected in the original are also selected in the template.