Installation

Process steps for the Jenkins plugin includes the following:

• Generate an Integration ID and Integration token.
• Install the plugin on your Jenkins instance.
• Populate the Jenkins configuration with Integration ID, Integration token, and Jenkins credentials.

1. On the HCL DevOps Velocity home page, click Settings > Integrations > Plugins and locate the Jenkins (Legacy) plugin in the table.
2. Click the Add integration button to display the Add Jenkins Integration window.
3. In the Enter a name to identify this integration from others field, enter a logical name representing the Jenkins instance you are connecting to HCL DevOps Velocity.
4. Click Create to generate an Integration ID and Integration token under Generated credentials.
5. In a text editor, copy and paste both the Integration ID and Integration token by clicking the copy to clipboard icon on the right side of each value.
6. Click Save.
7. In Jenkins on the left navigation pane, click Up > Manage Jenkins > Manage Plugins. Note: Manage Plugins is located in the System Configuration section of the page.
8. Navigate to hcl-accelerate.hpi and click the Download button to save the file.
9. In Jenkins on the Manage Plugins page, click the Advanced tab and in the Upload Plugin section, upload the file downloaded in the previous step.
10. On the Manage Jenkins page in the System Configuration section, click Configure System and locate the HCL DevOps Velocity section and perform the following:

1. Copy and paste the Integration ID and Integration token from your text editor into the respective fields.
2. In the Jenkins credentials drop-down, select and Add the required credentials.
3. If you are configuring Jenkins integrations on Kubernetes or Openshift instances, click the Advanced button, and in the Rabbit MQ Port field, enter the port number.
   Note: Typically, the port number is 31672 instead of the default value of 5672 that does not work.
4. Click the Save button.
5. Click the Test Connection button to validate your connection with HCL DevOps Velocity. Note: Upon successful connection, your data is accessible in HCL DevOps Velocity.

Manual build

To perform a manual build for the plugin directly from the GitHub repository, clone the repository from https://github.com/UrbanCode/hcl-accelerate-plugin

From the root directory, run either of the following commands:

• mvn install
• mvn clean package -DskipTests with the -DskipTests flag enabled to expedite the build without running tests

Note: The plugin requires Java 8 or later. To avoid potential errors, delete the target directory.

Usage

• Posting job metadata to your HCL DevOps Velocity instance – As you create and edit jobs, the metadata for the jobs is uploaded including the job names and parameter names so jobs can be invoked from HCL DevOps Velocity within the HCL DevOps Velocity security model.
• Invoke jobs from HCL DevOps Velocity – An authenticated, encrypted persistent connection is established with HCL DevOps Velocity so that you can trigger jobs and pipelines with no special firewall configuration.
• Updates status of running jobs – You will receive instant feedback in HCL DevOps Velocity with links to the execution.
• Job executions can create versions in the HCL DevOps Velocity pipeline – You will have the option to select Jenkins jobs as “input jobs” that create a version with special properties that you can specify.

Configuration properties

• Check gate in HCL DevOps Velocity
• Upload Build to HCL DevOps Velocity
• Upload Deployment to HCL DevOps Velocity
• Upload JUnit Results to HCL DevOps Velocity
• Upload JUnit Metrics File to HCL DevOps Velocity

Check gate in HCL DevOps Velocity

The CheckGate class is used to check gates applied on a particular stage of the HCL DevOps Velocity pipeline for a particular versionId of an application.

step($class: 'CheckGate',
pipelineId: "63a4591b-4d0d-4b8d-a6fb-4e9e7d79e754",
stageName: "DEV",
versionId: "NWZkOWUyZjYtOGE3Yy00NmJhLTlmZD-#48",
)

Pipeline script

Check gate input properties

Upload build to HCL DevOps Velocity

The UploadBuild class is used to upload build data to HCL DevOps Velocity. The revision parameter is important for linking the build to the work item via GitHub data (GIT_COMMIT in this case). The versionName is important for linking forward to deployments. The appName corresponds to the HCL DevOps Velocity pipeline application name.

step($class: 'UploadBuild',
tenantId: "5ade13625558f2c6688d15ce",
revision: "${GIT_COMMIT}",
appName: "${ACCELERATE_APP_NAME}",
versionName:"${currentBuild.displayName}",
requestor: "admin",
id: "${currentBuild.displayName}"
)

Pipeline script

Upload build input properties

Upload deployment to HCL DevOps Velocity

The UploadDeployment class is used to upload deployment data to HCL DevOps Velocity. The versionName parameter is critical for linking to build data. The appName corresponds to the HCL DevOps Velocity pipeline application name, while environmentName and environmentId are used to identify the deployment environment.

step([$class:
'UploadDeployment',
tenantId: "5ade13625558f2c6688d15ce",
versionName: "${currentBuild.displayName}",
versionExtId: "${currentBuild.displayName}",
type: 'Jenkins',
environmentId: "${ACCELERATE_ENV_ID_DEV}",
environmentName: 'DEV',
appName: "${ACCELERATE_APP_NAME}",
description: '[Description ex: Terraform Deployment]',
initiator: "admin",
result: 'true'
])

Pipeline script

Upload deployment input properties

Upload JUnit results to HCL DevOps Velocity

Upload metrics file to HCL DevOps Velocity

The UploadMetricsFile class is used to upload metrics file into HCL DevOps Velocity. The uploaded metrics file will be available in Insights in graphical form.

step($class: 'UploadMetricsFile',
tenantId: "5ade13625558f2c6688d15ce",
filePath: "junit.xml",
appName: "${ACCELERATE_APP_NAME}",
name:"Junit",
dataFormat: "junitXML",
pluginType: "junitXML",
testSetName: "Junit",
metricsRecordUrl: "${env.BUILD_URL}",
buildUrl: "${env.BUILD_URL}",
)

Pipeline script

Upload metrics file input properties