See our Templates repository for a list of ready to use Workflow Templates. You can also use these as reference for defining youur own Workflow Templates.
Getting started with Workflow Templates
You can define reusable templates for Workflows. All Workflow Templates are defined as Directed Acyclic Graphs (DAG), here's an example of how a DAG template is defined:
You can define and use parameters in your Workflow Templates. These parameters are displayed in the Workflow creation form (or are made available via CLI) and can be referenced in the template like so:
The syntax for parameter definitions are as follows:
If a parameter is defined,
value are required.
nameis the name of the parameters, only alphanumeric characters and
valueis the default value for the parameter
displayNameis the text that is displayed to the user
typeindicates how the parameter is rendered in the Workflow creation form in the Web UI. Possible values are:
input.textrenders a textbox
input.numberrenders a textbox that only accepts numbers
input.radiorenders radio buttons
select.selectrenders a dropdown
textarea.textarearenders a textarea
optionsdefine options if
When running Workflows, it is very common to have steps that generate or consume artifacts. Often, the output artifacts of one task may be used as input artifacts to a subsequent task.
Example below shows how you can download or upload artifacts from or to different object storage locations:
Artifacts can be packaged as Tarballs and gzipped by specifying an archive strategy, using the
You can also mark both input and output artifacts as optional by setting
true. In this case, if they don't exist, the Workflow will not throw an error: