Welcome
Releasing Software
A release is a repeatable plan that is used to drive deployments.
Properties
A deployment plan can contain user-defined properties. Properties values can be defined at design- or run-time.
Using properties
You can use properties in deployment plans, REST API endpoints, and external systems, such as ServiceNow®.

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.
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.
- 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.
  - Creating properties
    Creating properties
  - Using properties
    You can use properties in deployment plans, REST API endpoints, and external systems, such as ServiceNow®.
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

Using properties

You can use properties in deployment plans, REST API endpoints, and external systems, such as ServiceNow®.

Property examples

Use the following syntax to reference a property: `${propertyName}`. To escape the syntax pattern, use two dollar-sign symbols, $${...}. You set property values with the deployment plan's Properties page, REST API endpoints, or external systems, such as ServiceNow®.

The following table describes how to properties with task types.

Task type	Usage
ServiceNow	You can use the ServiceNow Output property field in a create change request action to store the change request ID in a property, for example, `'service_now_prod_ticket_id'`. Then, with another task, update the change request by referencing the property in the System ID field like this, `'${service_now_prod_ticket_id}'`.
Email	You can reference a system property in the email task Subject field, for example, `'${sys:release.name}' is complete!`.
Delayed	You can reference a delay task property in the Delay property field, for example, `'${prodTarget}'`. In this example, the task delays until the value in the `'${prodTarget}'` property is reached.

System properties

System properties enable you to access information about the parent release of a deployment plan. System properties can be referenced by any property-enabled task that is part of a release.

The following table contains the available system properties:

Table 1.
Property	Description
`${sys:release.name}`	The value in the release's Name field.
`${sys:release.description}`	Contains the content of the release's Description field.
`${sys:release.start}`	Release's Start time.
`$${sys:release.end}`	Contains the content of the release's End time field.

In the Email message field of an email-type task, you can reference system properties like this example:

Deployment for release `${sys:release.name}` - `${sys:release.description}` is complete.

You can reference a system property in a ServiceNow task's Short description field like this example:

Staging deployment `${sys:release.name}`.