-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable testsuite work in progress integration tests #19
Disable testsuite work in progress integration tests #19
Conversation
/test |
@fabiobrz: The
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test build |
@fabiobrz: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
61244db
to
68dcd96
Compare
68dcd96
to
ad9f245
Compare
…oyment for it to be used by WildFly 26 and EAP 7
… global-test.properties is filled in with required related properties
Temporary fix for the ProvisionerCleanupTestCase to handle the system:image-puller rolebinding removal, must be investigated
…e all the leftovers
…values for build and master namespaces
ad9f245
to
33bd34a
Compare
1e39200
to
bd8d354
Compare
LGTM, merging, thanks! |
Description
We're disabling all the integration tests that require for the global-test.properties file to be filled in with related properties.
Let's start with WildFly BootableJAR provisioner, and we'll incrementally re-enable the tests.
Here we also add a version of this test that is using a Javax based WildFly deployment, i.e. using WildFly 26.1.* bits.
This could help when testing Intersmash Bootable JAR provisioning tooling against EAP XP, rather than WildFLy, since the currently available bits and images (XP 4) seem still to be javax based.
This is also to verify that the OpenShift 4 tests will run on the OpenShift CI infra, see Onboarding Intersmash on OpenShift CI #18
Part of #21
Type of change
test, version modification, documentation, etc.)
Checklist