Skip to content

test: serve TeamCity over HTTPS in the full e2e stack - #269

Merged
matt-richardson merged 1 commit into
mainfrom
mr/e2e-https-teamcity
Oct 16, 2026
Merged

matt-richardson merged 1 commit into
mainfrom
mr/e2e-https-teamcity

Conversation

@matt-richardson

Copy link
Copy Markdown
Contributor

Part of DPT-3630 (Renaming an Octopus space breaks TeamCity configurations that name it). Split out of #265 (feat: list spaces for a connection that authenticates with OIDC) to keep that PR to the OIDC work.

Why

#265's e2e test lists spaces through an OIDC connection. The OIDC plugin only issues tokens for an HTTPS issuer, and Octopus fetches the issuer's signing keys from TeamCity's root URL. The full stack now runs a Caddy proxy that serves TeamCity over HTTPS with a certificate from Caddy's own CA, Octopus trusts that CA, and TeamCity's root URL points at the proxy.

Notes

  • Every full-stack e2e test runs on this stack. I ran the whole e2e suite locally against the real containers: 17 classes, 24 tests, all green.
  • The stacks that start only TeamCity, or TeamCity and an agent, get the same root URL but no proxy. None of the tests on those stacks use the root URL.

🤖 Generated with Claude Code

A Caddy proxy serves TeamCity over HTTPS with a certificate Octopus trusts,
and TeamCity's root URL points at the proxy. The OIDC plugin only issues
tokens for an HTTPS issuer, and Octopus fetches the issuer's signing keys from
that address; an e2e test of an OIDC connection needs both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@matt-richardson
matt-richardson merged commit 42113c4 into main Oct 16, 2026
7 checks passed
@matt-richardson
matt-richardson deleted the mr/e2e-https-teamcity branch October 16, 2026 04:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants