You can use a test task to test a deployment. When you register a Jenkins Server endpoint, you connect to a Jenkins server to start a build job from a release pipeline.


If you have existing artifacts in the Jenkins server you cannot access them from vRealize Code Stream.

If you configure a Jenkins test job to fail if test failures occur, then the release pipeline also fails.

Verify that the Jenkins server endpoint is registered. See the Installation and Configuration guide.

Verify that the Jenkins server version is 1.561 or later.


Click the Code Stream tab.


Select an existing pipeline to configure from the Pipeline tab.


Select Edit > Stages.


Select Add Task.


Select Test from the Categorydrop-down menu.


Select Jenkins from the Provider drop-down menu.


Select the Jenkins server endpoint you registered from the drop-down menu.


Enter a name for the test task and click OK.


Select the new task from the stage column.


Confirm to save the pipeline.


Select an Execute Task for the release pipeline.




Runs the release pipeline task without conditions.

On Condition(s)

Runs the release pipeline task only if the defined condition is evaluated as true. If the condition is false, the task is skipped.

A boolean expression using the following operands and operators is supported.

Pipeline variables such as, ${pipeline.variableName}. Curly brackets are reserved for specifying pipeline variables.

Task output variables such as, ${Stage1.task1.machines.value.hostIp}

Default pipeline constant variables such as, ${releasePipelineName}

Case insensitive Boolean values such as, true, false, 'true', 'false'

Integer or decimal values without quotes

String values used with single or double quotes such as, "test", 'test'

String and Numeric types of values such as, == Equals and != Not Equals

Relational operators such as, > , >=, <, and <=

Boolean logic such as, && and ||

Arithmetic operators such as, +, -, *, and /

Nested expressions using round brackets

Strings with literal value ABCD is evaluated as false and the task is skipped.

Unary operators are not supported.

A sample condition, ${Stage1.task1.output} == “Passed” || ${pipeline.variableName} == 39


(Optional) Select the Continue Pipeline execution even if this task fails option.

This option allows the release pipeline to bypass the failed task and continue with the execution process.


Select the Jenkins job from the Jobs drop-down menu.


Enter the Jenkins job input properties.


Click the text box and enter ${ .

The associated variables appear in the drop-down menu.


Select the variable.


(Optional) Enter a period next to the variable to view the task name in the drop-down menu.


(Optional) Enter a period next to the task name to view the task output or pipeline parameters in the drop-down menu.

For example, the input property variable can be ${StageName.test.JobName}.


(Optional) Select one or more Jenkins job output properties to expose to other tasks in the pipeline.

For example, you can expose the Jenkins job name and the test results in a custom task.


Click Save.

The following task output format is an example for a test task.

            "name": "buildId",
            "type": "STRING",
            "description": "Build Id",
            "value": "4"
            "name": "jobUrl",
            "type": "STRING",
            "description": "Job Url",
            "value": ""
            "name": "estimatedDuration",
            "type": "NUMBER",
            "description": "Estimation time to complete the build",
            "value": "2332343"
            "name": "jobName",
            "type": "STRING",
            "description": "Job Name",
            "value": "dummy"
            "name": "testResult",
            "type": "JSON",
            "description": "Job Name",
            "value": {
                "totalCount": 40,
                "skipCount": 0,
                "failureCount": 0,
                "successCount": 40