To connect and interact vRealize Code Stream with external systems, you must install a plug-in. Each plug-in that you install requires that you configure the endpoint and enter specific endpoint definitions. For example, to provision a virtual machine, vRealize Code Stream requires a vRealize Automation endpoint to facilitate the communication.

After you define and configure the plug-in endpoint, you can create a corresponding task in the release pipeline. In the task, you define parameters. Then, when you execute a pipeline, you can access the custom workflow in the vRealize Orchestrator client.

For example, a vRealize Automation endpoint allows for a provisioning task to be configured. A Jenkins endpoint allows for a task to configure the Jenkins job as part of the pipeline template.

vRealize Code Stream supports the following endpoint types.

Table 1. Endpoint Types

Endpoint Type



Register an Artifactory Server Endpoint


Register a Jenkins Server Endpoint

vRealize Automation Server

Register a vRealize Automation Server Endpoint

vRealize Orchestrator Workflow for Task

Register a vRealize Orchestrator Workflow for a Task

vRealize Orchestrator Server

Register a vRealize Orchestrator Server Endpoint

vRealize Orchestrator Workflow for Gating Rule

Register a vRealize Orchestrator Workflow for a Gating Rule

Team Foundation Server

Register a Microsoft Team Foundation Server Endpoint

Cloud Foundry Server

Register a Cloud Foundry Server Endpoint

Bamboo Server

Register a Bamboo Server Endpoint

Bugzilla Server

Register a Bugzilla Server Endpoint

JIRA Server

Register a JIRA Server Endpoint