Skip to main content

tw pipelines

Manage pipelines

Run tw pipelines -h to view the list of supported operations.

Pipelines define pre-configured workflows in a workspace. A pipeline consists of a workflow repository, launch parameters, and a compute environment.

tw pipelines list

List pipelines

tw pipelines list [OPTIONS]

Options

OptionDescriptionRequiredDefault
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
-l, --labelsShow labels.Nofalse
-f, --filterShow only pipelines that contain the given wordNo
--visibilityShow pipelines: all, private, shared [default: private].Noprivate
--pagePage number for paginated results (default: 1)No
--offsetRow offset for paginated results (default: 0)No
--maxMaximum number of records to display (default: 100)No

tw pipelines add

Add a pipeline

tw pipelines add [OPTIONS] <PIPELINE_URL>

Arguments

ArgumentDescriptionRequired
PIPELINE_URLNextflow pipeline URLYes

Options

OptionDescriptionRequiredDefault
-n, --namePipeline name. Must be unique within the workspace.Yes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
-d, --descriptionPipeline description.No
--version-nameInitial pipeline version name.No
--labelsLabels to apply to the resource. Provide comma-separated label values (use key=value format for resource labels). Labels will be created if they don't existNo
--pipeline-schema-idPipeline schema identifier to use.No
-c, --compute-envCompute environment identifier where the pipeline will run. Defaults to workspace primary compute environment if omitted. Provide the name or identifier.No
--work-dirWork directory path where workflow intermediate files are stored. Defaults to compute environment work directory if omitted.No
-p, --profileArray of Nextflow configuration profile names to apply.No
--params-filePipeline parameters in JSON or YAML format. Provide the path to a file containing the content.No
--revisionGit revision, branch, or tag to use. Use --commit-id to pin to a specific commit within the revision.No
--commit-idSpecific Git commit hash to pin the pipeline execution to.No
--configNextflow configuration as text (overrides config files). Provide the path to a file containing the content.No
--pre-runAdd a script that executes in the nf-launch script prior to invoking Nextflow processes. See: https://docs.seqera.io/platform-cloud/launch/advanced#pre-and-post-run-scripts. Provide the path to a file containing the content.No
--post-runAdd a script that executes after all Nextflow processes have completed. See: https://docs.seqera.io/platform-cloud/launch/advanced#pre-and-post-run-scripts. Provide the path to a file containing the content.No
--pull-latestPull the latest version of the pipeline from the repository.No
--stub-runExecute a stub run for testing (processes return dummy results).No
--main-scriptAlternative main script filename. Default: main.nf.No
--entry-nameWorkflow entry point name when using Nextflow DSL2.No
--schema-nameName of the pipeline schema to use.No
--user-secretsArray of user secrets to make available to the pipeline.No
--workspace-secretsArray of workspace secrets to make available to the pipeline.No

Run tw pipelines add -h to view the required and optional fields for adding your pipeline.

Add a pre-configured pipeline to the Launchpad:

tw pipelines add --name=my_rnaseq_nf_pipeline \
--params-file=my_rnaseq_nf_pipeline_params.yaml \
--config=<path/to/nextflow/conf/file> \
https://github.com/nextflow-io/rnaseq-nf

New pipeline 'my_rnaseq_nf_pipeline' added at user workspace

The optional --params-file flag is used to pass a set of default parameters that will be associated with the pipeline in the Launchpad.

The optional --config flag is used to pass a custom Nextflow configuration file — configuration values passed here override the same values in the default pipeline repository nextflow.conf file. When this flag is set, all configuration values specified in Platform pipeline or compute environment Nextflow config fields are ignored.

tip

The params-file or --config file must be a YAML or JSON file using Nextflow configuration syntax.

tw pipelines delete

Remove a pipeline

tw pipelines delete [OPTIONS]

Options

OptionDescriptionRequiredDefault
-i, --idPipeline identifierYes
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No

tw pipelines view

View pipeline details

tw pipelines view [OPTIONS]

Options

OptionDescriptionRequiredDefault
-i, --idPipeline identifierYes
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
--version-idPipeline version identifierYes
--version-namePipeline version nameYes

tw pipelines update

Update a pipeline

tw pipelines update [OPTIONS]

Options

OptionDescriptionRequiredDefault
-i, --idPipeline identifierYes
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
-d, --descriptionPipeline descriptionNo
--new-namePipeline new nameNo
-c, --compute-envCompute environment identifier where the pipeline will run. Defaults to workspace primary compute environment if omitted. Provide the name or identifier.No
--work-dirWork directory path where workflow intermediate files are stored. Defaults to compute environment work directory if omitted.No
-p, --profileArray of Nextflow configuration profile names to apply.No
--params-filePipeline parameters in JSON or YAML format. Provide the path to a file containing the content.No
--revisionGit revision, branch, or tag to use. Use --commit-id to pin to a specific commit within the revision.No
--commit-idSpecific Git commit hash to pin the pipeline execution to.No
--configNextflow configuration as text (overrides config files). Provide the path to a file containing the content.No
--pre-runAdd a script that executes in the nf-launch script prior to invoking Nextflow processes. See: https://docs.seqera.io/platform-cloud/launch/advanced#pre-and-post-run-scripts. Provide the path to a file containing the content.No
--post-runAdd a script that executes after all Nextflow processes have completed. See: https://docs.seqera.io/platform-cloud/launch/advanced#pre-and-post-run-scripts. Provide the path to a file containing the content.No
--pull-latestPull the latest version of the pipeline from the repository.No
--stub-runExecute a stub run for testing (processes return dummy results).No
--main-scriptAlternative main script filename. Default: main.nf.No
--entry-nameWorkflow entry point name when using Nextflow DSL2.No
--schema-nameName of the pipeline schema to use.No
--user-secretsArray of user secrets to make available to the pipeline.No
--workspace-secretsArray of workspace secrets to make available to the pipeline.No
--pipeline-schema-idPipeline schema identifier to use.No
--pipelineNextflow pipeline URLNo
--allow-draftIf versionable fields change, keep the new version as an unnamed draft instead of auto-naming and promoting it to default.No
--version-idPipeline version identifierYes
--version-namePipeline version nameYes

The default launch parameters can be changed with the update command:

tw pipelines update --name=my_rnaseq_nf_pipeline \
--params-file=my_rnaseq_nf_pipeline_params_2.yaml

tw pipelines export

Export a pipeline

tw pipelines export [OPTIONS] [FILENAME]

Arguments

ArgumentDescriptionRequired
FILENAMEFile name to exportNo

Options

OptionDescriptionRequiredDefault
-i, --idPipeline identifierYes
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
--version-idPipeline version identifierYes
--version-namePipeline version nameYes

Export a pipeline configuration as JSON for scripting and reproducibility.

Command:

tw pipelines export --name=my_rnaseq_nf_pipeline my_rnaseq_nf_pipeline_v1.json

Example output:

Pipeline exported into 'my_rnaseq_nf_pipeline_v1.json'

tw pipelines import

Add a pipeline from file content

tw pipelines import [OPTIONS] <FILENAME>

Arguments

ArgumentDescriptionRequired
FILENAMEFile name to importYes

Options

OptionDescriptionRequiredDefault
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
-c, --compute-envCompute environment name (defaults to value defined in JSON compute environment file)No
--overwriteOverwrite the pipeline if it already exists.Nofalse

Import a pipeline into a workspace from a previously exported JSON file.

Command:

tw pipelines import --name=my_rnaseq_nf_pipeline_v1 ./my_rnaseq_nf_pipeline_v1.json

Example output:

New pipeline 'my_rnaseq_nf_pipeline_v1' added at user workspace

tw pipelines labels

Manage pipeline labels

tw pipelines labels [OPTIONS] [labels]

Arguments

ArgumentDescriptionRequired
&lt;labels&gt;Comma-separated list of labels.No

Options

OptionDescriptionRequiredDefault
-i, --idPipeline identifierYes
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
--no-createAssign labels without creating the ones which were not found.No
--operations, -oType of operation (set, append, delete) [default: set].Noset

tw pipelines versions

Manage pipeline versions

tw pipelines versions

tw pipelines versions list

List pipeline versions

tw pipelines versions list [OPTIONS]

Options

OptionDescriptionRequiredDefault
-i, --idPipeline identifierYes
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
-f, --filterSearch pipeline versions by name prefix. Also supports keyword filters: versionName, versionId, versionHash. Multiple filters can be combined e.g. 'myPipeline versionName:<name> versionHash:<hash>'.No
--is-publishedShow only published pipeline versions if true, draft versions only if false, all versions by defaultNo
--full-hashShow full-length hash values without truncationNo
--pagePage number for paginated results (default: 1)No
--offsetRow offset for paginated results (default: 0)No
--maxMaximum number of records to display (default: 100)No

tw pipelines versions manage

Manage a pipeline version name or default version status

tw pipelines versions manage [OPTIONS]

Options

OptionDescriptionRequiredDefault
-i, --idPipeline identifierYes
-n, --namePipeline nameYes
-w, --workspaceWorkspace numeric identifier or reference in OrganizationName/WorkspaceName format (defaults to TOWER_WORKSPACE_ID environment variable)No
--version-idPipeline version identifierYes
--version-namePipeline version nameYes
--new-nameNew name for the pipeline versionNo
--set-defaultSet this version as the defaultNo