FlexDeploy Workflow editor and certain Plugins support use of Variables, Project and Environment Instance Properties, which helps build dynamic steps in Build / Deploy processes. This document provides details of available variables and their meaning. In addition to Shell script, FlexDeploy also supports Groovy, Ant, and WLST (Jython) scripts, which allows access to additional Java object variables.
Variable Scope
Overall, it makes sense to use unique names for any user defined variable to avoid confusion.
- Project, Target, Instance Properties
- Scope is entire workflow execution.
- Ideally you should not modify these properties during workflow execution, but it can be modified to influence execution if necessary.
- FlexFields
- Scope of FlexField value is entire workflow execution, which may be build/deploy/utility.
- Note that build request FlexFields are associated with Project Version created by build, hence those values are available during deploy execution as well for project version.
- Do not modify during course of workflow execution.
- Workflow Inputs
- Scope is entire workflow execution.
- Do not modify during course of workflow execution.
- Workflow Variables
- Scope is entire workflow execution.
- You can modify value for variables during workflow execution and use it to pass various values to plugin inputs or capture plugin outputs.
- Plugin Inputs
- Scope is specific plugin execution for endpoint.
- User defined Plugin Inputs and Outputs
- Scope is specific plugin execution for endpoint.
- Use unique names for Workflow Inputs, Variables and any user defined Plugin Input or Outputs to avoid any confusion.