You can run tests or other jobs by using the Jenkins plug-in that allows you to use custom automation and scripts.

You can use any Jenkins job in the Jenkins server in the release pipeline with this endpoint enabled. You can use this endpoint to invoke a Jenkins build job during the modeling of a release pipeline and execute the job as part of the release pipeline.

Verify that the Jenkins server is available and configured with or without SSL.

Verify that the Jenkins server version is 1.561 or later.

Verify that the Jenkins jobs are created in the Jenkins server with the input string parameter, VRCSTestExecutionId.

Log in to the vRealize Automation console as a system administrator or release manager.


Select Administration > Orchestration Configuration > Endpoints.


Click Add.


Select Jenkins (Code Stream) from the Plug-In drop-down menu and click Next.


Enter a Jenkins server endpoint name and an applicable description.

For example, in the description section you can add the release pipeline name that uses this Jenkins server endpoint.


Click Next.


Enter the Jenkins server configuration details.



Jenkins Instance Name

Enter the Jenkins instance name.

For example,

User Credentials

User name and password for the Jenkins server.


Enter the host URL as protocol://host:port.

Sample host URL,

Polling Interval

Time that the task must wait to check the progress.

Request Retry Count

Number of times to retry the scheduled build request for the Jenkins server.

Retry Wait Time

Seconds to wait before retrying the build request for the Jenkins server.

Offline Creation

Require a validation and certificate acceptance when the endpoint is created.

You can accept the default setting or select Yes from the drop-down menu to enable this configuration.


Click Add.


Click the Code Stream tab in vRealize Automation to continue with the task configuration.

Create a test task to use this endpoint in the release pipeline. See the Using vRealize Code Stream guide.