wildfly
Kubernetes testing
-
Set up a Kubernetes cluster (using Kind) with an image registry and an ingress controller
-
Build container images using wildfly:image goal and push them to the cluster image registry
-
Add an ingress to access the application (until https://github.com/wildfly/wildfly-charts/issues/52 is resolved)
-
Add tests for helloworld & todo-backend
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@kabir @emmartins This PR is not meant to be merged but this shows how we could use a local Kubernetes cluster to test the QuickStarts. I did if for the simplest one (helloworld) and the most complex one (todo-backend).
It does not rely on S2I to build the application image and use the wildfly:image goal instead.
@jmesnil: No presubmit jobs available for wildfly/quickstart@main
In response to this:
/test all
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.
You can see executions of the action at https://github.com/jmesnil/quickstart/actions/workflows/testing.yml
@jmesnil: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/wildfly-quickstart-e2e | a6c07039a8a60d9d3d3ce5753c8468793a28e1c1 | link | true | /test wildfly-quickstart-e2e |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.