Repository navigation
Conversation
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
force-pushed
the
pin-the-v2-version-main
branch
from
November 18, 2026 21:38
9a698cf to
99e94e4
Compare
This branch has not been deployed
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.
Newer CAPI releases disable the CC V2 API: from capi chart 1.249.1-1 on, V2 is behind
cloudController.config.temporaryEnableV2(defaultfalse), 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:6b6882c(v0.26.0 can't deploy charts ≥ 1.249.1-1, their values schema changed)-Dgroups=v2-DexcludedGroups=v2,SKIP_V2_TESTS=trueresolve-capi-version.shis replaced byresolve-latest-capi-chart.sh(anonymous ghcr.io tag listing).Integration tests
@RequiresV2Apialso tags tests with JUnit tagv2(696 of 921 tests, checked with a JUnit discovery run).@IfCloudFoundryVersioncompares 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
Testing
./mvnw -Pintegration-test -DskipTests spotless:check installpasses. The integration tests haven't run against a live CF yet; this PR's CI run is the first.