Step options for Generic, PowerShell, and Python plugins
Important: Although the content in this topics is relevant for this version of XL Deploy, we recommend that you use the rules system for customizing deployment plans. For more information, see Getting started with XL Deploy rules.
If you create a plugin based on the Generic or PowerShell plugin, you can specify step options that control the data that is sent when performing a
NOOP deployment step defined by a configuration item (CI) type. Step options also control the variables that are available in templates or scripts.
A step option specifies the extra resources that are available when performing a deployment step. A step option is typically used when the step executes a script on a remote host. This script, or the action to be performed, may have zero or more of the following requirements:
- The artifact associated with this step needed in the step’s
- External file(s) in the
- Resolved FreeMarker template(s) in the
- Details of the previously deployed artifact in a variable in the script context.
- Details of the deployed application in a variable in the script context.
The type definition must specify the external files and templates involved by setting its
templateClasspathResources properties. For example, see the
shellScript delegate in the Generic plugin. Information on the previously deployed artifact and deployed application are available when applicable.
For some types, especially types based on the Generic plugin, the default behavior is that all classpath resources are uploaded and all FreeMarker templates are resolved and uploaded, regardless of the deployment step type. These resources may result in a large amount of data, especially if the artifact is large. For some steps, you may not need to upload all resources.
For example, creating the deployed on the target machine may involve executing a complex script that needs the artifact and some external files, modifying it involves a template, but deleting the deployed is completed by removing a file from a fixed location. In this case, it is not necessary to upload everything each time, because it is not all needed.
Step options enable you to use the
noopOptions properties on a type, and to specify the resources to upload before executing the step itself.
If you want a deployment script to refer to the previous deployed, or to have information about the deployed application. You can make this information available by setting the step options.
The following step options are available for the Generic plugin and PowerShell plugin:
none: Do not upload anything extra as part of this step. You can also use this option to unset step options from a supertype.
uploadArtifactData: Upload the artifact associated with this deployed to the working directory before executing this step.
uploadClasspathResources: Upload the classpath resources, as specified by the deployed type, to the working directory when executing this step.
The following additional step option is available in the Generic plugin:
uploadTemplateClasspathResources: Resolve the template classpath resources, as specified by the deployed type, then upload the result into the working directory when executing this step.
The following additional step option is available in the PowerShell plugin:
exposePreviousDeployed: Add the
previousDeployedvariable to the PowerShell context. This variable points to the previous version of the deployed CI, which must not be null.
exposeDeployedApplication: Add the
deployedApplicationvariable to PowerShell context, which describes the version, environment, and deployeds of the currently deployed application. Refer to the
udm.DeployedApplicationCI for more information.
Your plugin CI types can use step options when they inherit from one of the following Generic or PowerShell plugin deployed types:
These types provide the hidden
noopOptions that your type inherits.
XL Deploy comes with various predefined CI types based on the Generic and the PowerShell plugins. For the default settings of
noopOptions, see Generic Plugin Manual and PowerShell Plugin Manual.
You can override the default type definitions settings in the
synthetic.xml file. You can change the defaults in the
exposeDeployedApplication: Add the
deployedApplicationobject to the Python context (
There are no additional classpath resources in the Python plugin, so only the current deployed is uploaded to a working directory when the Python script is executed.