Skip to content

feat: Run the V2 integration tests against a dedicated CAPI version - #1409

Open
ZPascal wants to merge 1 commit into
cloudfoundry:mainfrom
ZPascal:pin-the-v2-version-main
Open

ZPascal wants to merge 1 commit into
cloudfoundry:mainfrom
ZPascal:pin-the-v2-version-main

Conversation

@ZPascal

@ZPascal ZPascal commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Newer CAPI releases disable the CC V2 API: from capi chart 1.249.1-1 on, V2 is behind cloudController.config.temporaryEnableV2 (default false), and kind-deployment main no longer enables it (cloudfoundry/kind-deployment#540). This splits the integration tests so V3 runs against the latest CAPI while V2 keeps a dedicated version. The 5.x.x counterpart is #1408.

Changes

Workflow (integration-test.yml): the matrix is now Java × api:

v2 job v3 job
CAPI pinned to chart 1.249.0 (last chart serving V2) latest capi chart, resolved at runtime (currently 1.252.1-1)
kind-deployment v0.26.0 main @ 6b6882c (v0.26.0 can't deploy charts ≥ 1.249.1-1, their values schema changed)
Tests -Dgroups=v2 -DexcludedGroups=v2, SKIP_V2_TESTS=true
Preview / schedule stays pinned other components use their latest versions

resolve-capi-version.sh is replaced by resolve-latest-capi-chart.sh (anonymous ghcr.io tag listing).

Integration tests

  • @RequiresV2Api also tags tests with JUnit tag v2 (696 of 921 tests, checked with a JUnit discovery run).
  • @IfCloudFoundryVersion compares 2.x versions with the server's V2 API version and 3.x versions with its V3 API version. Before, all gates were compared with one V2-first version, so e.g. UsersTest (PCF_4_v3) was skipped on every server with V2 enabled. With V2 disabled, the server counts as newer than every 2.x version, as before.

Client: SUPPORTED_API_VERSION = 2.299.0 (CAPI 1.249.0), SUPPORTED_API_VERSION_V3 = 3.237.0 (CAPI 1.252.0).

Notes

  • Each run now has twice as many jobs (8 instead of 4 with the default Java matrix).
  • Since the v3 job follows the latest chart, a future capi values change can break it until kind-deployment catches up.

Testing

  • ./mvnw -Pintegration-test -DskipTests spotless:check install passes. The integration tests haven't run against a live CF yet; this PR's CI run is the first.

Newer CAPI releases disable the CC V2 API, so the integration tests are split:

- V2 tests (@RequiresV2Api, now tagged "v2") run against the pinned capi chart
  1.249.0, the last one serving V2, on kind-deployment v0.26.0.
- All other tests run against the latest capi chart, resolved at runtime, on a
  newer kind-deployment with SKIP_V2_TESTS=true.
- @IfCloudFoundryVersion compares 2.x versions with the V2 and 3.x versions with
  the V3 API version of the server, so V3 gates such as PCF_4_v3 no longer get
  compared with the V2 version.
- SUPPORTED_API_VERSION is 2.299.0 (CAPI 1.249.0), SUPPORTED_API_VERSION_V3 is
  3.237.0 (CAPI 1.252.0).
@ZPascal
ZPascal force-pushed the pin-the-v2-version-main branch from 9a698cf to 99e94e4 Compare November 18, 2026 21:38

This branch has not been deployed

No deployments
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