CA Technologies Run RA Deployment Plan
The CA Release Automation Plug-In lets you create a deployment out of a deployment plan and run it on a specific environment.
Usage
The extension installs the following components:
- A service endpoint for connecting to the RA Server.
- A RA Run Deployment task, to run an RA deployment out of a deployment plan.
Follow the steps given below to setup the extension and to use it properly.
Note: This extension is compatible with TFS 2015 update 2.1 (and above) and RA 6.1 (and above).
Create a CA Release Automation Server endpoint
Visual Studio Team Services or Team Foundation Server requires a service connection to a RA Server to run deployments.
- Open the Services tab in your Visual Studio Team Services or Team Foundations Server Control Panel.
- From the New Service Endpoint list, select CA Release Automation Server.
- In the Add New CA Release Automation Server Connection pop-up dialog, provide the required details to connect to the RA Server:
- Provide a user friendly name for the service endpoint in the Connection Name like Nolio.
* Enter the RA Server URL, like http://nolio-server:8080/ or https://nolio-secured-server:8443/. Note that port is needed.
* Enter a Username and Password that has the required access to the RA Server. Press OK to create the connection.
Run an existing deployment plan
Lets say you have a Nolio application called 'Online services' and as part of the 'Web-application' project you want to deploy this sprint (sprint 7) latest build (number 56) to the QA environment.
In order to do so follow the next steps:
- Open your build or release definition and add the RA - Run Deployment Plan task. The task can be found in the Deploy section of the Add Tasks dialog.
To run an existing deployment plan, fill-in the task parameters as described below:
- RA Service Connection: In the dropdown, select the RA Server connection that was created above.
- Strategy: In the dropdown, select the 'Run Existing Deployment Plan' option.
- Deployment Plan Name: The existing deployment plan name you have created in Nolio.
- Application Name: Nolio Application name.
- Project Name: The Nolio Project which the deployment plan related to.
- Build Name: The deployment plan build number as you defined when creating the deployment plan, not TFS build number.
- Deployment Name: The name of the new created deployment. Note that you may use TFS variables in all of these fields.
- Deployment Stage To Perform: The deployment stage you wish to execute. All The preceding stages will be executed..
- Environment: The name of the environment to deploy on.
Leave the advanced options empty as it relevant only for Create new Deployment Plan strategy.
Create and run a new Deployment Plan
Lets say you have a Nolio application called 'Online services' and as part of the 'Web-application' project you want to deploy a template of the latest build to the QA environment.
In order to do so follow the next steps:
Open your build or release definition and add the RA - Run Deployment Plan task just as described above.
To run a new Deployment Plan, fill-in the task parameters as described below:
- RA Service Connection: In the dropdown, select the RA Server connection that was created above.
- Strategy: In the dropdown, select the 'Create new Deployment Plan' option.
- Application Name: Nolio Application name.
- Project Name: The Nolio Project which the deployment plan should related to.
- Template Name: TThe existing Template name you have created in Nolio.
- Deployment Template Name: The existing Deployment Template name you have created in Nolio.
- Deployment Plan Name: The name of the new created deployment plan. Note that you may use TFS variables in all of these fields
- Build Name: The deployment plan build number. Use '$(Build.BuildNumber)' for TFS build number.
- Deployment Name: The name of the new created deployment.
- Deployment Stage To Perform: The deployment stage you wish to execute. All The preceding stages will be executed..
- Environment: The name of the environment to deploy on.
- Timeout: Maximum time to wait for Nolio Server to finish the deployment, default is 0 - meaning no timeout.
You may also add these optional advanced fields in Create new Deployment Plan mode:
- Artifact Package: Add an artifact package to the new Deployment Plan. You can use an existing package or an XML which will create a new one.
- Manifest: Add a XML Manifest to supply values for Nolio Release Parameters.
- Properties: Add a pairs of key-value to supply values to Nolio Template Properties.
Legal Notice
This product is owned and/or licensed by CA Technologies (“CA”).
An active license agreement for CA Release Automation (“License Agreement”) is required for its use.
Your use of this product is governed by the terms of the License Agreement.
If you do not have an active License Agreement with CA, you may not use this product.
For details, please contact CA.
