-
Notifications
You must be signed in to change notification settings - Fork 3k
Use a specific Keycloak docker image tag to run the integration tests #5537
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
Conversation
Thanks @jaikiran. CI seems to be still failing for native test too, can you have a look?
We'll need to disable it too. Thanks. |
Interesting. I had thought that since the I've updated this PR to explicitly disable |
So it now fails for
I guess we'll have to wait for someone with knowledge of these tests to take a look. |
We probably need another way to handle it. Maybe the |
@jaikiran Actually a specific tag version was removed after Pedro's fix which made it unnecessary at a time. Can you please add |
@jaikiran Latest tag was created 2 days ago which could explain why the tests started failing. So pinning it to |
…ation tests against
@sberyozkin, thank you for that information. I think that indeed is the root cause of these failures. I have updated this PR to undo the disabling of the tests and instead use a specific Keycloak docker image tag |
I am closing this for now, as I had already submitted #5547 which also updates the fabric8 docker plugin used outside CI. |
The commit here temporarily disables theBearerTokenAuthorizationTest
since it has been failing consistently in recent runs causing CI failures for other unrleated PRs.Once the real issue is fixed, this can then be re-enabled.The PR has now been updated to use
7.0.1
of Keycloak docker image to run these tests, instead of the "latest" which since the past 2 days has now moved to 8.0.0 and has been causing failures in the Keycloak related tests.