feat: add pipeline versioning support by JaimeSeqLabs · Pull Request #582 · seqeralabs/tower-cli

JaimeSeqLabs · 2026-02-19T20:54:07Z

Summary

Adds pipelines versions subcommand group (list, view, update) to manage pipeline versions
Wires --version-id / --version-name into existing commands: pipelines view, pipelines export, pipelines update, and launch
pipelines add gains --version-name to name the initial version on creation
pipelines update detects when a versionable field change creates a new version: auto-generates a name (mirroring the frontend naming algorithm), assigns it, and promotes it to default. Use --allow-draft to skip auto-naming and keep the new version as an unnamed draft for manual management.
pipelines view displays version info (name, default flag, hash) when a version is specified
pipelines export includes the version name in the exported JSON so it survives import round-trips
Moves pipelines labels commands into a labels/ sub-package mirroring the versions/ structure

Test plan

./gradlew test — all unit tests pass
TOWER_CLI=./build/native/nativeCompile/tw ./gradlew test — all unit tests pass in binary mode
Manual E2E testing against a Platform backend (see testing guidelines below)

Testing guidelines

Setup

export TOWER_ACCESS_TOKEN="<your-token>"
export TOWER_API_ENDPOINT="<your-platform-api-url>"

PIPELINE_NAME="AutoTest"
PIPELINE_URL="https://github.com/pditommaso/nf-sleep"

# Build the CLI native binary
./gradlew nativeCompile
TW="./build/native/nativeCompile/tw"
# when targeting localhost instance
# TW="./build/native/nativeCompile/tw --insecure"

Test 1: Create pipeline with initial version name

$TW pipelines add -n "$PIPELINE_NAME" --version-name "v1.0" "$PIPELINE_URL"

Verify: Pipeline is created successfully.

Test 2: List versions

$TW pipelines versions list -n "$PIPELINE_NAME"
$TW pipelines versions list -n "$PIPELINE_NAME" --filter "v1.0"
$TW pipelines versions list -n "$PIPELINE_NAME" --is-published
$TW pipelines versions list -n "$PIPELINE_NAME" --max 10 --offset 0

Verify: All list variants return v1.0 as the single published version.

Test 3: View version by name and by ID

$TW pipelines versions view -n "$PIPELINE_NAME" --version-name "v1.0"

VERSION_ID=$($TW -o json pipelines versions list -n "$PIPELINE_NAME" 2>/dev/null \
  | jq -r '.versions[0].id')

$TW pipelines versions view -n "$PIPELINE_NAME" --version-id "$VERSION_ID"

Verify: Both show version details (ID, name, hash, default flag, creator, timestamps).

Test 4: View pipeline with version targeting

$TW pipelines view -n "$PIPELINE_NAME" --version-name "v1.0"
$TW pipelines view -n "$PIPELINE_NAME" --version-id "$VERSION_ID"
$TW pipelines view -n "$PIPELINE_NAME"

Verify: The first two show Version Name, Version Is Default, and Version Hash rows. The third (no version) omits version info.

Test 5: Update non-versionable field (no new version)

$TW pipelines update -n "$PIPELINE_NAME" -d "Updated description"

Verify: Output says "Pipeline updated" without any new version message.

Test 6: Update versionable field (auto-names and promotes new version)

$TW pipelines update -n "$PIPELINE_NAME" --main-script "main.nf"

Verify: Output says "Pipeline updated" followed by "New version 'v1.0-1' created and set as default, available in the Launchpad." (name is derived from the current default version name).

Test 7: Confirm auto-named version appears in version list

$TW pipelines versions list -n "$PIPELINE_NAME"

Verify: Two published versions shown — v1.0 and v1.0-1 (or similar). The new one is marked as default.

Test 7b: Update versionable field with --allow-draft (keeps unnamed draft)

DRAFT_ID=$($TW -o json pipelines update -n "$PIPELINE_NAME" --main-script "main.nf" --allow-draft 2>/dev/null \
  | jq -r '.draftVersionId')
echo "Draft version ID: $DRAFT_ID"

Verify: DRAFT_ID is a non-null version ID. Output includes "New draft version created" message.

Test 8: Rename draft version

$TW pipelines versions update -n "$PIPELINE_NAME" --version-id "$DRAFT_ID" --new-name "v2.0"

Verify: Version updated successfully.

Test 9: Set version as default

$TW pipelines versions update -n "$PIPELINE_NAME" --version-name "v2.0" --set-default

Verify: Version updated successfully.

Test 10: Update a specific version by name

$TW pipelines update -n "$PIPELINE_NAME" --version-name "v1.0" -d "Non-versionable change to v1.0"

Verify: Pipeline updated without creating a new draft.

Test 11: Export with version targeting

$TW pipelines export -n "$PIPELINE_NAME" --version-name "v1.0"
$TW pipelines export -n "$PIPELINE_NAME" --version-id "$VERSION_ID"
$TW pipelines export -n "$PIPELINE_NAME"

Verify: The first two include "version": {"name": "v1.0"} in the JSON. The third (default version) omits the version field.

Test 12: Export + import round-trip

EXPORT_FILE=$(mktemp /tmp/pipeline-export-XXXXXX.json)
$TW pipelines export -n "$PIPELINE_NAME" --version-name "v1.0" "$EXPORT_FILE"
$TW pipelines import -n "${PIPELINE_NAME}_imported" "$EXPORT_FILE"
$TW pipelines view -n "${PIPELINE_NAME}_imported"
$TW pipelines delete -n "${PIPELINE_NAME}_imported"
rm -f "$EXPORT_FILE"

Verify: Imported pipeline exists and can be viewed.

Cleanup

$TW pipelines delete -n "$PIPELINE_NAME"

…ling

…dling

…t versions are created after updates

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/main/java/io/seqera/tower/cli/commands/pipelines/versions/ListCmd.java

...n/java/io/seqera/tower/cli/responses/pipelines/versions/ListPipelineVersionsCmdResponse.java

src/test/java/io/seqera/tower/cli/pipelines/PipelineVersionsCmdTest.java

… trigger a draft version

src/main/java/io/seqera/tower/cli/commands/pipelines/UpdateCmd.java

…versioning-support

tcrespog

Tested and worked successfully.

tcrespog · 2026-02-25T07:09:49Z

src/main/java/io/seqera/tower/cli/commands/pipelines/UpdateCmd.java

+        //  - Server already named it (fixed API) → just report it.
+        //  - Unnamed draft + --allow-draft       → report draft ID, let user manage it manually.
+        //  - Unnamed draft (default behavior)    → auto-generate a name, assign it, and promote to default
+        //    (mirrors the frontend naming algorithm from version-name-resolver.ts).


I think there's no need to reference the explicit file name where the algorithm is supposedly implemented here.

tcrespog · 2026-02-25T07:13:59Z

src/main/java/io/seqera/tower/cli/commands/pipelines/UpdateCmd.java

+
+    /**
+     * Names an unnamed draft version and promotes it to default. This mirrors the frontend's
+     * behavior in version-name-resolver.ts: derive an incremental name from the current default


Similar comment about referencing explicit file names in another project.

tcrespog · 2026-02-25T07:23:02Z

src/main/java/io/seqera/tower/cli/commands/pipelines/UpdateCmd.java

+        // Query published versions and find the one marked as default. We use the published filter
+        // because draft versions should not be considered as the "current default" for naming.
+        ListPipelineVersionsResponse versionsResponse = pipelineVersionsApi()
+                .listPipelineVersions(pipelineId, wspId, null, null, null, true);


Given that all published versions are retrieved here, there would be an edge case with the max page size on the server side (although it is large) in case the default version is not found in the first page. Anyway, can't we assume the default version if the launch.id attached to the pipeline? Isn't that what determines that the version is the default one?

tcrespog · 2026-02-25T07:33:00Z

src/main/java/io/seqera/tower/cli/utils/VersionNameHelper.java

+     * Strips trailing -{number}, increments (or starts at 1).
+     * E.g., "pipeline-3" → "pipeline-4", "rnaseq" → "rnaseq-1"
+     */
+    public static String generateNextVersionName(String baseName) {


This method seems to be used only here and for testing: it might be worth making it protected or package-private (no access modifier).

JaimeSeqLabs added 24 commits February 17, 2026 20:52

feat: add pipeline version API client to the base abstract cmd

fd648cc

feat: utility classes update

86d0181

feat: pipeline versions list cmd

7403f26

fix: missing license header

ff8a78c

feat: unit test for pipeline versions cmd

ed4aef5

chore: move error handler into base class

935d716

feat: pipeline versions view cmd

649fb06

feat: pipeline version update cmd

2557c3b

feat: include commands in the root versioning class

67c0a77

feat: unit tests for versions view and update cmds

ee94e58

fix: remove unsetting default flag use case, update version by name

4de3e48

chore: move version resolution to base api cmd

627b72a

feat: versioning support for 'pipelines add' cmd, refactor error hand…

4080fc6

…ling

feat: versioning support for 'pipelines view' cmd, refactor error han…

f8c6d46

…dling

feat: versioning support for 'pipelines export' cmd

aebd939

feat: versioning support for 'pipelines launch' cmd

a1534f0

feat: versioning support for 'pipelines update' cmd, detect when draf…

6acd7b9

…t versions are created after updates

feat: updated unit tests

840a7ce

feat: updated reflection files

d7c9857

feat: include versioning data in 'pipelines export' cmd ouput

845818e

feat: include versioning data in 'pipelines view' cmd output

510a6a8

feat: update tests with versioning data output

838be74

refactor: move pipeline labels subcommands to separate package

8cdca25

fix: reflection files

63358de

JaimeSeqLabs requested review from swingingsimian and tcrespog February 19, 2026 21:00

merge: resolve conflicts with master (pipelineSchemaId)

56d36d8

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

tcrespog reviewed Feb 20, 2026

View reviewed changes

JaimeSeqLabs added 2 commits February 23, 2026 21:50

fix: ensure retro-compatibility, auto name and promote if the changes…

5104931

… trigger a draft version

refactor: clarify filter parameter

03ab185

JaimeSeqLabs added 2 commits February 23, 2026 22:15

refactor: add version ID to the version list output

12ec5c0

test: cleanup test comments [ci skip]

bf0a97a

tcrespog reviewed Feb 24, 2026

View reviewed changes

src/main/java/io/seqera/tower/cli/commands/pipelines/UpdateCmd.java Show resolved Hide resolved

Merge remote-tracking branch 'origin/master' into PLAT-3660-pipeline-…

ebe2d3e

…versioning-support

tcrespog approved these changes Feb 25, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

feat: add pipeline versioning support#582

feat: add pipeline versioning support#582
JaimeSeqLabs wants to merge 30 commits intomasterfrom
PLAT-3660-pipeline-versioning-support

JaimeSeqLabs commented Feb 19, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

tcrespog left a comment

Uh oh!

tcrespog Feb 25, 2026

Uh oh!

tcrespog Feb 25, 2026

Uh oh!

tcrespog Feb 25, 2026 •

edited

Loading

Uh oh!

tcrespog Feb 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Comments

Conversation

JaimeSeqLabs commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Testing guidelines

Setup

Test 1: Create pipeline with initial version name

Test 2: List versions

Test 3: View version by name and by ID

Test 4: View pipeline with version targeting

Test 5: Update non-versionable field (no new version)

Test 6: Update versionable field (auto-names and promotes new version)

Test 7: Confirm auto-named version appears in version list

Test 7b: Update versionable field with --allow-draft (keeps unnamed draft)

Test 8: Rename draft version

Test 9: Set version as default

Test 10: Update a specific version by name

Test 11: Export with version targeting

Test 12: Export + import round-trip

Cleanup

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

tcrespog left a comment

Choose a reason for hiding this comment

Uh oh!

tcrespog Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

tcrespog Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

tcrespog Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tcrespog Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

JaimeSeqLabs commented Feb 19, 2026 •

edited

Loading

tcrespog Feb 25, 2026 •

edited

Loading