During an upgrade from vRealize Code Stream 1.0 to vRealize Code Stream 1.2, 2.1, 2.2, or the current version, existing endpoints are added to the appliance, and the format of the release pipeline variables is updated.

Artifactory Endpoints and Pipeline

After the upgrade, you must add the external Artifactory details to the new default endpoint that you created. See Migrate Artifacts and Configure Your External Artifactory Instance.

Before the upgrade, if you had pipelines that included an Artifactory task, those pipelines go into Draft state after the upgrade. As a result, you must activate and run those pipelines.

Jenkins Server and vRealize Automation Server Endpoints

vRealize Code Stream retrieves all the existing endpoints for Jenkins Server, vRealize Automation Server, and Team Foundation Server (TFS) from vRealize Orchestrator, and adds them as new entries. The endpoints appear in vRealize Automation at Administration > vRealize Orchestrator Configuration > Endpoints.

The names of the server endpoints are updated as follows:

  • Jenkins server endpoint name is prefixed with Jenkins_EndpointName.

  • vRealize Automation server endpoint name is prefixed with Vra_EndpointName.

Release Pipeline Variables

In the current version, the property name format has changed.

During the upgrade to the current version, the format of the existing release pipeline properties are updated. For example, $RP1 is updated to ${pipeline.RP1}, and $RP2 is updated to ${pipeline.RP2}.

Task Output Variables

During the upgrade, the format of the existing task output variable values such as $CustomScriptName_OUTPUT are updated to ${StageName.TaskName.outputConfig} in the release pipeline.

Variable Names

During the upgrade, the format of each variable name for manual approval in custom tasks is updated.

Table 1. Variable Name Values

Pre-upgrade Format

Post-upgrade Format

$ReleasePipelineName

${releasePipelineName}

$StageName

${stageName}

$NextStageName

${nextStageName}

$TaskName

${taskName}

$NextTaskName

${nextTaskName}

Variable Concatenation

During the upgrade, the format of variable values that are concatenated such as $RP1 with output $CustomScriptName_OUTPUT, are updated to ${pipeline.RP1} with output ${StageName.TaskName.outputConfig}.