Hello all, repeatedly I've been fixing issues in CI related to startup of keycloak dev service when quarkus-oidc dependency is present in the project.
We don't actually use that dev service, instead, we rely on KeycloakQuarkusTestResource.java from our kogito quarkus test utils module. Big difference is that the kogito class has extended timeout while waiting for keycloak startup, thus preventing env-related failures. On the other hand the quarkus dev service has default startup 60 seconds and that is not overridden - resulting in repeated CI failures. This time I've reported as https://github.com/apache/incubator-kie-kogito-examples/issues/1976 , but it's an ad-hoc solution. We could apply a workaround to use an env variable in CI, but that doesn't solve the problem of us running something we don't actually use. I think it would be worth reviewing all the devservices that are being started for the quarkus extensions during our builds and consider if they're utilized - because this is a possible waste of resources (because there's always a docker container started). Is anyone available to do such a review? Regards Jan
