Skip to content

ci(agent-e2e): track shared E2E_TEST_OSS_CONDUCTOR_VERSION org var - #533

Open
nthmost-orkes wants to merge 1 commit into
mainfrom
ci/track-shared-oss-version
Open

nthmost-orkes wants to merge 1 commit into
mainfrom
ci/track-shared-oss-version

Conversation

@nthmost-orkes

Copy link
Copy Markdown
Contributor

What

Point agent-e2e.yml at the org-level E2E_TEST_OSS_CONDUCTOR_VERSION variable instead of the never-created CONDUCTOR_SERVER_VERSION, and bump the fork-PR fallback to 3.33.0.

Why

CONDUCTOR_SERVER_VERSION was never provisioned as an org variable, so this workflow has been running on its hardcoded fallback the entire time. E2E_TEST_OSS_CONDUCTOR_VERSION is the variable that already drives the docker-compose e2e in pull_request.yml, and conductor's publish.yml now bumps it on every release (conductor-oss/conductor#1764). Reading the same variable makes agent-e2e track the just-released server automatically.

A concrete release is valid as both a Docker Hub tag and a Maven Central boot-JAR artifact, so one variable serves both e2e paths. It must stay a real version -- latest has no Maven Central artifact, which is exactly what broke this path while the org var still held latest.

Note

This replaces python-sdk's deliberate hardcoded pin (3.32.0-rc18). It now auto-tracks the shared org variable like the java/javascript/csharp agent-e2e workflows, for a single source of truth across all four SDKs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant