The step's command element specifies the scripting tool that will perform the step and identifies the file containing the actual script. The
agent that will perform the step will download the plug-in and expect to find the script among the downloaded files. Of course,
the agent must also have access to the scripting tool. Any other arguments required by the script/tool can also be specified
with the arg file attribute. The arg file attributes should be defined in the order compatible with the scripting tool.
The Create File command script is written in Groovy. Groovy is a Java-like scripting language.
This command instructs the Groovy interpreter to run create_file.groovy (more about Groovy and the particulars of this file in the following section).
This line (which is part of every command):
<arg file="${PLUGIN_INPUT_PROPS}"/>
sends a file containing the properties required by the step to the agent. The properties in the file are those furnished
at run-time and others defined earlier that are required by the step. See Figure 80, “Properties”. The ${PLUGIN_INPUT_PROPS} variable resolves to the location of this uDeploy-managed properties file.
And this line (which is also part of every command):
<arg file="${PLUGIN_OUTPUT_PROPS}"/>
refers to the file returned by the agent after finishing the step. The properties in this file are available to later steps
in the process. The ${PLUGIN_OUTPUT_PROPS} variable resolves to the location of this uDeploy-managed properties file.
