testcontainer timeout in gitlab pipeline #42360
Unanswered
tilothiele
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
addendum - better subject: 'How to fix testcontainer timeout in gitlab pipeline?'
I got haunted by a timeout only when starting a Keycloak testcontainer in my gitlab pipeline only.
mvn test
runs perfect on my local machine.Log in my pipeline:
2024-08-07 12:36:26,302 INFO [tc.qua.io/.0.4] (build-38) Container quay.io/keycloak/keycloak:24.0.4 started in PT55.67264304S 2024-08-07 12:36:33,127 ERROR [io.qua.oid.dep.dev.key.KeycloakDevServicesProcessor] (build-38) Realm quarkus can not be created: io.smallrye.mutiny.TimeoutException
in application.properties I already put the line
quarkus.devservices.timeout=10m
Without any change. It seems that the keycloak container started but was'nt yet ready to serve api calls in this environment. Is there another place to set a waiting time?
As other containers (eg. postgresql) works fine in the pipeline, I guess this issue is not related to my gitlab runner.
I know I can put a file .testcontainers.properties in the project root. But I couldn't find an appropriate setting.
Can so help me out with a helpful hint? (uh - living without a pipeline is really annoying)
Beta Was this translation helpful? Give feedback.
All reactions