Conversation
ZPascal
force-pushed
the
gh-integration-test-matrix
branch
3 times, most recently
from
October 3, 2026 20:57
615240c to
4ca27c7
Compare
ZPascal
force-pushed
the
gh-integration-test-matrix
branch
from
October 3, 2026 21:00
4ca27c7 to
ce9223f
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.
Adds a GitHub Actions workflow that runs the integration tests on Java 8, 11, 17 and 21. It's preparation for moving the release pipeline from Concourse to GitHub Actions, so the test step does what the Concourse
integration-testtask does:integration-testprofile,TEST_SKIPSSLVALIDATION=true,TEST_QUOTAS_ROUTES_RESERVEDPORTS=50.There's no shared CF environment. Each job starts its own Cloud Foundry on KinD (kind-deployment), so no secrets and no Shepherd lease are needed, and the matrix jobs can run in parallel.
api.cf.127-0-0-1.nip.io, userccadminand theadminUAA client. The passwords are theCC_ADMIN_PASSWORDandUAA_ADMIN_SECRETvalues that the setup exports.ci-java.yml, not from the Broadcom Artifactory mirror.setup-cfaction into the workflow and pinned kind-deployment to a commit, instead of using the action. The action always checks out kind-deploymentmain, and since cloud-provider-kind 0.12.0 (Update registry.k8s.io/cloud-provider-kind/cloud-controller-manager Docker tag to v0.12.0 kind-deployment#511) the gateway isn't reachable on 127.0.0.1:443, somake loginfails. fix: Revert cloud-provider-kind to v0.11.1 kind-deployment#512 reverts that bump, and Add ref input to setup-cf action kind-deployment#513 adds arefinput so the action can be pinned by commit. After both are in, this can become a plainuses:with a SHA.Setup and login work in a manual run (Java 8, 11, 17, 21). The tests don't pass yet: 903 ran, 79 failed, 355 errored, in about 17 minutes. Two causes in the log:
CF-AppBitsUploadInvalid(160001): missing :resourceswhen the test config pushes apps (testLogCacheApp,serviceBrokerId). This takes out whole classes like bothServiceInstancesTestclasses andBlobstoresTest.JsonParsingException: Found unexpected property suspendedforSpaceResource, which breaksRoutesTest,TasksTestand others.Both look like the client being behind the CAPI version in the KinD deployment. That's a separate topic, so the workflow goes in as a base, and these failures are known.