-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Improve the way OIDC init failures are handled - 1.13 #17662
Conversation
I've seen Gradle tests failing in my fork as well |
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building c5c2d18
Full information is available in the Build summary check run. Test Failures⚙️ Gradle Tests - JDK 11 Linux #📦 integration-tests/gradle✖ ✖ ✖ ✖ ✖ ⚙️ Gradle Tests - JDK 11 Windows #📦 integration-tests/gradle✖ ✖ ✖ ✖ ✖ |
@glefloch do we need to backport some Gradle fix to |
Sounds good. Mind opening a PR when you have some time? Thanks |
yes I will open one against |
@sberyozkin the commit fixing those tests has been backported, can you test with it? |
@glefloch Thanks, the failures are not related, but sure, let me rebase, hopefully it will make this PR greener :-) |
c5c2d18
to
30929c4
Compare
Looks much better now, only hibernate-validator test is failing but it is not related to this PR |
Hey Pedro @pedroigor Can you please check this backport in case it will have to be merged to |
This backports #16773 with the following differences:
1.13.x
keycloak.url
property - it has been fixed in themain
as part of some other PR - it is needed for the PR relatedoidc-wiremock
tests to pass in1.13.x