Job plugins
Node Steps
- Jira Node Step Plugins (Enterprise)
- Command step
- Script step
- Scipt file
- Script url
- Job reference
- Copy file
- Local command
- Data node
- SQL Runner (Enterprise)
- VMWare Operations Node Step Plugin (Enterprise)
Workflow Steps
- Ansible module
- Ansible playbook inline
- Ansible playbook
- Global variable
- Flow control
- Job state conditional
- Log data step
- Refresh project nodes
- Data step
- File Transfer ()
- Github (Enterprise)
- Jira Workflow Step Plugins (Enterprise)
- Progress Badge (Enterprise)
- ServiceNow (Enterprise)
- VMWare Step Plugins (Enterprise)
Notifications
Notification plugins determine what Rundeck does when a Job Execution starts or finishes, with either success or failure. For a general explanation on how job notifications work, see Creating jobs#Job Notifications
Workflow Strategy
The Workflow Strategy determines how the steps are processed within a Job's Workflow.
Node Orchestrator
An Orchestrator plugin can determine how to use the Nodes selected by your Job Filter. By default, all of the filtered nodes will be used, in the order specified in your Job definition.
However an Orchestrator plugin can choose which of the nodes should be used, and when. For example, to limit concurrent execution to a subset of the nodes, or to skip certain nodes.
Log Filters
Log Filters can filter/process/read output from specific Workflow Steps, or all Workflow Steps of a Job.
Content Converters
Content Converters are not added directly to Jobs, but can be used by Log Filters and Step plugins.
← Job options Nodes →