Rundeck executes Command items on Nodes. The command may be part of a Workflow as defined in a Job, and it may be executed multiple times on different nodes.
Several "kinds" of Command items can be specified in Workflows:
Rundeck uses the NodeExecutor and FileCopier services as part of the process of executing these command types.
The procedure for executing an "exec" command is:
The procedure for executing a "script" command is:
When executing a Script step, the destination file path to be used when copying the script can be set using Node, Project, or Framework configuration values.
Node Attributes:
file-copy-destination-dir
: The directory on the remote node to copy the script file to before executing it. The default value is C:/WINDOWS/TEMP/
on Windows nodes, and /tmp
for other nodes.osFamily
: specify "windows" for windows nodes.The file-copy-destination-dir
can be set at the project and framework level, and can have a default be specified depending on the osfamily as well:
In project.properties
file:
project.file-copy-destination-dir
- default for all nodes in projectproject.file-copy-destination-dir.[osfamily]
- default for nodes in the project with specified osfamilyIn framework.properties
file:
framework.file-copy-destination-dir
- default for all nodes in frameworkframework.file-copy-destination-dir.[osfamily]
- default for nodes in the framework with specified osfamilyThe order to determine the value is:
Rundeck includes the following node execution plugins.
local
local execution of a command.
jsch-ssh
remote execution of a command via SSH, requiring the "hostname", and "username" attributes on a node.
For FileCopier, these plugins:
local
creates a local temp file for a script.
jsch-scp
remote copy of a command via SCP, requiring the "hostname" and "username" attributes on a node.