ci(agent-e2e): drop Agentspan server JAR, run against conductor-oss#424
Merged
Conversation
added 2 commits
July 14, 2026 11:13
conductor-oss ships the agent runtime by default from 3.32.0-rc.8, so the e2e server leg no longer needs the Agentspan release JAR. Server download switches to the conductor-oss boot jar (Maven Central); the Agentspan CLI binary stays on its own separate pin since test_suite16_cli_skills.py still drives it against this same server.
CONDUCTOR_OSS_VERSION -> CONDUCTOR_SERVER_VERSION and AGENTSPAN_CLI_VERSION 0.4.3 -> 0.4.4, matching the already-agreed CI shape in idea-13/design.md (analysis workspace, not shipped here) rather than inventing new names.
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
…-testkit preflight conductor-oss's standalone server serves secrets from the process env, so PUT/DELETE /api/secrets/* return 500 "env-backed secrets are read-only". This never surfaced while e2e ran against the writable agentspan server; switching to conductor-oss exposed it as 4 CI failures (suite2, suite4, suite26). Mirrors the assumption-skip already shipped in the Java/C# ports: CredentialsCLI.set() and test_suite26's _put_secret() skip (not fail) on a "read-only" response body; CredentialsCLI.delete() additionally tolerates "read-only" as best-effort cleanup, same as it already does for "not found". Also widens test_suite5's mcp-testkit --help preflight from a 5s timeout that only caught FileNotFoundError to 15s + catching TimeoutExpired too — a separate, likely-environmental flake surfaced in the same CI run.
NicholasDCole
approved these changes
Jul 14, 2026
v1r3n
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
conductor-ossships the agent runtime by default from3.32.0-rc.8onward, so the e2e workflow no longer needs to boot the Agentspan release JAR as the test server.agent-e2e.yml's server download switches from the Agentspan GitHub release asset to theconductor-ossMaven Central boot jar (conductor-server-<version>-boot.jar).AGENTSPAN_CLI_VERSION) —e2e/test_suite16_cli_skills.pystill drives it against this same server.CONDUCTOR_SERVER_VERSION/AGENTSPAN_CLI_VERSION) since they're no longer tied to the same release train.permissions: contents: readblock (least privilege — the token is only used for the public CLI release download).e2e/conftest.py'sruntimeMetadatacapability-probe comments updated to reference the new pin name — the probe itself is server-agnostic and required no logic change.Why
Matches the CI shape already used by this SDK's sibling ports (Java/C#/TS
agent-e2e.yml, all similarly moving off the Agentspan server JAR) —conductor-ossis now the reference server for agent e2e, not Agentspan.Test plan
agent-e2e)conftest.py's capability probe already worked against any server flavor before this change.