• Overview
  • Documentation
  • Version history

Description

The YAML Executor plug-in automates the initial setup process for integrating different CI/CD tools into HCL DevOps Velocity. You can define the integration configurations in a YAML file and apply it in HCL DevOps Velocity to automate the integration process.

Quick Info

Product icon

Product

HCL DevOps Velocity (HCL Accelerate)
Plugin type icon

Type

plugin
Compatibility icon

Compatibility

HCL DevOps Velocity 4.0.12 or later
created by icon

Created by

HCLSoftware
Website icon

Website

Published Date

Last Updated

Summary

The YAML Executor plug-in is automatically installed and configured without manual configuration. You can apply the YAML file under Settings>External Config Pipeline to initiate the YAML Executor plug-in integration process.

Steps

Importing YAML configuration file into HCL DevOps Velocity

Import the YAML configuration file into HCL DevOps Velocity by using any one of the following methods:

Method 1: Using GitHub plug-in

Integrate HCL DevOps Velocity with a GitHub repository that contains the ucv.yml file to import the YAML configuration file into HCL DevOps Velocity.

Perform the following steps to import the YAML configuration file using GitHub plug-in:

  1. Log in to HCL DevOps Velocity.
  2. Click Settings>Integrations.
  3. In the Installed tab, click Add Integration for the installed GitHub plug-in.
    Note: If the GitHub plug-in is not installed, go to Available tab and click Install for GitHub plug-in.

  1. Enter the details in the required fields to add GitHub integration.

  1. Click Add to save the details and enable the integration.
    The YAML configuration file from the GitHub repository is automatically synced to HCL DevOps Velocity and displayed under Settings>External config pipeline.

Method 2: Using user interface

You can import the YAML configuration file into HCL DevOps Velocity using user interface if it is not hosted in a GitHub repository.

Perform the following steps to add YAML configuration file using user interface:

  1. Log in to HCL DevOps Velocity.
  2. Click Settings>External Config Pipeline.
  3. Click Download sample yaml to download the sample YAML file.
  4. Edit the sample file with the actual values of your configuration.
  5. Click Add new config file.

  1. Add New Config dialog opens.
  2. Click Choose file to select the edited file.

  1. Click Confirm to upload the file.

  1. The uploaded YAML configuration file is displayed in the list.

  1. To edit the existing YAML configuration file, perform the following steps:
    1. Click overflow menu of the YAML configuration file and then click Edit.
  2. The existing YAML configuration file will download.
  1. Edit the downloaded YAML configuration file.
  1. Click overflow menu of the YAML configuration file which you have edited and then click Update.
    Update config dialog opens.
  1. Click Choose file to select the edited file.

  1. Click Confirm to upload the file.

  1. The updated YAML configuration file is displayed in the list.

Applying YAML configuration file

Once you have the YAML configuration file in HCL DevOps Velocity, perform the following steps to apply the configuration:

  1. Log in to HCL DevOps Velocity.
  2. Click Settings>External Config Pipeline.
  3. Choose the required YAML configuration file in the list and click right angle bracket to preview the configuration details.

  1. Click Apply for the required YAML configuration file.
  2. Click overflow menu for the required YAML configuration file and then click View Logs to view the logs of the applied YAML configuration file.

Configuration properties

The YAML configuration file is used to define configuration settings for automating the initial setup process for integrating various CI/CD tools into HCL DevOps Velocity.

YAML File Structure

The following table describe the properties used to define the configuration in the YAML file.

Property name Type Description Required
version String The version number of YAML file. Yes
integrations Array List of integration configurations. Yes

 

Integrations

The following table describe the properties that you must define under integrations:

Property name Type Description Required
type String Type or category of the CI/CD tool. Yes
attributes Object Additional attributes specific to the integration. Yes
configs Object Configuration object for the integration. Yes

Configuration Object

The following table describe the properties that you must define under configs :

Property name Type Description Required
name String Name of the configuration. Yes
loggingLevel String Logging level for the integration. Yes
deltaTime String Optional: Time difference for the integration. Yes

The following table describe the properties that you must define under configs :For additional configuration properties depending on integration type, navigate to the respective plug-in and look for the general configuration properties section for more details.

Sample YAML configuration file

Following is the sample YAML configuration file with existing integrations:


version: 0.0.1
integrations:
  - tenant_id: 12345-12345
    name: Valuestream 1
    attributes:
      appEnvOrder:
        - DEV
        - QA
        - PROD
      directSync: true
      auto-config: true
      integrationId: 12345-12345
      team: Dev Team
      applications:
        - TL5
      applicationids:
        - 12345-12345
    type: ucv-ext-launch
    
  • To filter a pipeline by application in a value stream, add “applications” and “teams” to map the value stream to a team.
  • If `integrationId` is specified, then `configs` is optional. `name` parameter to override value stream name.
  • Set the `directSync` attribute to “true” to enable direct synchronization during execution (currently it is supported only for devops deploy plugin).
  • If `directSync` is enabled, the `applicationids` property is mandatory to selectively sync the required applications.

Replace the property values in the sample file with the actual values specific to your configuration.

Customizing YAML configuration file

Perform the following steps to customize the YAML configuration file for your required integrations:

  1. Open the YAML configuration file in a text editor.
  2. Update version property with the appropriate version number.
  3. Under integrations property, add or remove any property as required.
  4. For each integration, add typeattributes, and configs property. name is optional if you want to overwrite the valuestream name.
  5. In valuestream, to filter the pipeline based on the application, add applications and teams to map valuestream against the team.
  6. Under configs property, you must add the required properties based on the integration type. If integrationId is specified then configs is optional.
  7. To order the environment while syncing, use the appEnvOrder property.
  8. Set the auto-config attribute to true for enabling automatic setup of pipeline applications processes and environments after creating a new integration.
  9. Save the YAML configuration file.

Compatibility Matrix

The following table lists the compatibility versions of the YAML Executor plug-in and Velocity

DevOps Velocity version YAML Executor plug-in version
5.2.5 or later 0.0.15
5.2.2 to 5.2.4 0.0.14
5.1.6 to 5.2.1 0.0.13
4.0.0 to 5.1.5 0.0.12

ucv-ext-yaml-executor 0.0.15.tar

Uploaded: 07-September-2026 12:00

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-yaml-executor:0.0.15

 

Release Notes

  • Feature enhancement: Introduced direct synchronization capability during YAML execution. YAML Executor no longer depends on the completion of the full background synchronization process for initial value stream creation. (Currently supported for devops deploy plugin).
  • Added new parameters: Added the following new parameters to support direct synchronization.
    • DirectSync: Enables direct synchronization during YAML execution. The YAML Executor validates resource existence in velocity before requesting data from the devops deploy plug-in.
    • Applicationids: Specifies the list of application IDs to selectively synchronize, and reduce synchronization overhead. This parameter is mandatory when directSync is enabled.

ucv-ext-yaml-executor:0.0.13

 

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-yaml-executor:0.0.13

 

Release Notes

  • Bug fix: Resolved an issue where userAccessKey was not reliably fetched during concurrent requests in the measure. This caused some requests to fail or not execute until retried. The YAML Executor plugin now runs all requests consistently as expected.

ucv-ext-yaml-executor:0.0.12

 

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-yaml-executor:0.0.12

 

Release Notes

  • Bug fix: The issue involving the triggering of the existing integrated Deploy plug-in through the YAML Executor plug-in has been resolved.

ucv-ext-yaml-executor:0.0.11

 

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-yaml-executor:0.0.11
 

Release Notes

  • Feature enhancement: Added a new parameter, appEnvOrder, within the attributes section of the configuration. This parameter enables users to explicitly specify the sequence in which environments are created, ensuring that the environment creation process adheres to the defined order.

ucv-ext-yaml-executor:0.0.8

 

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-yaml-executor:0.0.8
 

Release Notes

  • Improvisation : Plug-in synchronization has been optimized to align with scheduled events, with particular emphasis on the end time. Additionally, failure scenarios related to pipeline creation and value stream processing have been resolved.

ucv-ext-yaml-executor:0.0.7

Added extra parameter: Added below new parameters to configure valuestream.

  • name: Specify the name for the ValueStream.
  • application: Filter resources to include only the specified application in the pipeline section.
  • integrationId: Reuse an existing integration configuration. If integrationId specified then configs field is optional.
  • team: Associate the ValueStream with a specific team.
  • appEnvOrder: To order the environment in the valuestream pipeline while syncing

ucv-ext-yaml-executor:0.0.6

Uploaded: 01-Sep-2023 11:11

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-yaml-executor:0.0.6
 

Release Notes

  • Started using timeSpan for Initial Sync date.

ucv-ext-yaml-executor:0.0.5

Uploaded: 02-Jun-2023 07:48

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-yaml-executor:0.0.5
 

Release Notes

  • Initial Release

Related Plugins