Automation deployment tasks integrate with Serena Release Automation and Serena Release Automation, powered by Nolio, to automate installation and configuration tasks. This section tells how to create a Serena Release Automation, powered by Nolio, deployment task. For information on creating a Serena Release Automation, powered by Nolio, deployment task, see Creating Release Automation Deployment Tasks .
You can create a Serena Release Automation, powered by Nolio, deployment task, which is used to deploy a deployment unit for a release package into a particular stage.
You can do the following:
Associate the task to a release package stage.
Specify the application involved in the tasks.
Specify application parameters to pass to specific environments.
Specify the target environment on which to run the tasks.
Specify the process to be executed in the environment.
Specify owners for the task.
The sequence number is used to specify order of execution of the deployment tasks. The automation deployment task is specific to a single stage. Each set of application parameters is for a specific server.
To execute an automation deployment task for installation and configuration of files through Serena Release Automation, Serena Release Manager needs information on the application, application parameters, environment, and process.
To create a Release Automation (Nolio) deployment task:
From a release package or deployment process template view, navigate to the Deployment tab and then select the Deployment tasks tab.
Select a stage for which this task will be executed.
Click Create Task.
The Create Deployment Task form appears.
In Task Type, select Release Automation (Nolio).
The Task Type: Automation form appears.
Fill out the Automation form.
For example:
Enter Task name and Sequence number.
Click Get application to refresh the list of applications stored in Release Automation (Nolio) and then select an application.
Click Get environment to refresh the list of environments for the selected application and then select an environment.
Click Get process to refresh the list of processes for the selected environments and then select a process.
In the Release Automation Parameters section, enter parameters and the list of servers to which you want to pass these parameters. You can specify only servers that are already defined in Release Automation (Nolio).
Parameters use the following format:
<variable_name1>=<variable_data1>&<variable_name2>=<variable_data2>
Example parameters:
var1=test1&var2=test2
Example servers:
Server1=lab1_computer
Server2=lab3_computer
Specify the Schedule execution time, the date and time at which you want the deployment task to be initiated.
Select the primary and secondary owners for the task.
Optionally enter a description.
Click OK.
The automation deployment task is saved. It will be executed according to its sequential order when the release package to which it is associated is deployed to the specified stage.
NOTE
The Release Manager default implementation supports only variables for Release Automation (Nolio) application parameters; it does not support variables for server parameters.
When you specify clients for your server, only client names that are assigned to your server in Release Automation (Nolio) may be included. For example, if in Release Automation (Nolio) Server2 is defined to include both max_computer and my_lab_test, both of these may be specified in the parameter. For example:
Server2=max_computer&Server2=my_lab_test
Example
The Serena Release Manager automation deployment task relates directly to the corresponding configuration in Release Automation (Nolio) as shown in the following figure.