Overview
Seqera Platform provides version-controlled, access-controlled, reproducible execution of Nextflow pipelines.
When you add a pipeline to Seqera, you define:
- The pipeline Git repository and revision (branch, tag, or commit)
- Compute environment for execution
- Pipeline parameters and configuration profiles
- (Optional) Labels, resource labels, and secrets
- (Optional) Pre-run and post-run bash scripts that execute in your compute environment
Manage pipelines
Key features
Pipeline revision management
Workflow repositories change over time as code is updated. Seqera provides revision management features, such as commit ID pinning to ensure reproducible execution by locking pipelines to specific Git commits, and Pull latest controls to instruct Nextflow to fetch the most recent commit at execution time.
Pipeline outputs and reports
After a run completes, the Outputs tab on the run details page shows the files the pipeline produced. It contains up to two sub-tabs:
- Pipeline outputs — Output files declared using the Nextflow workflow output syntax, with lineage IDs and labels that link each file back to the run that produced it. This sub-tab requires data lineage enabled in the workspace or on the individual run, and a pipeline using the Nextflow workflow output syntax (Nextflow 24.10.0 or later).
- Reports — Named report files configured via
tower.yml, visible for all runs where reports are set up. See Reports to configure this.
Pipeline versioning
Seqera's pipeline versioning system automatically tracks pipeline configuration changes as draft versions, creating an immutable audit trail of your pipeline evolution. Publish drafts to make important configurations easy to identify, share, and promote across your team. Version checksums provide cryptographic verification that workflow runs match their associated pipeline configurations.