-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[WFLY-18163] Add org.wildfly.extension.elytron.jaas-realm module exclusion #17044
Conversation
...on/elytron/src/test/java/org/wildfly/test/integration/elytron/realm/JaasCustomRealmTest.java
Outdated
Show resolved
Hide resolved
...on/elytron/src/test/java/org/wildfly/test/integration/elytron/realm/JaasCustomRealmTest.java
Outdated
Show resolved
Hide resolved
...on/elytron/src/test/java/org/wildfly/test/integration/elytron/realm/JaasCustomRealmTest.java
Outdated
Show resolved
Hide resolved
@OndrejKotek Thank you for review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Skyllarr! Approving these changes. We'll need to discuss how to coordinate getting wildfly/wildfly-core#5587 merged once pre-checked since CI passing will depend on the exclusions that are being added in this PR.
I have split this PR so that the CI passes on this one. The test was moved to the new PR #17417 . It might be easier to coordinate the merges with wildfly/wildfly-core#5587 |
Hi @yersan , I was trying to make HostExcludesTestCase work, so I created WFLY-18764 issue and included its commit in this PR. But now I can't get pass the below error in "Thin Server Build": Invalid value WildFly30.0 for host-release; legal values are [WildFly23.0, WildFly24.0, WildFly25.0, WildFly26.0, WildFly20.0, WildFly21.0, WildFly22.0, WildFly27.0, WildFly28.0, WildFly29.0, WildFly12.0, WildFly13.0, WildFly14.0, WildFly15.0, WildFly10.0, WildFly10.1, WildFly11.0, EAP6.3, EAP7.2, EAP6.2, EAP7.1, EAP7.0, WildFly16.0, WildFly17.0, EAP7.4, WildFly18.0, EAP6.4, EAP7.3, WildFly19.0]"}}} do you happen to know why the WildFly30.0 is not an allowed value? Thanks a lot! |
Hi @Skyllarr , the changes in the HostExclusion test case and domain exclusions look good, the issue you are facing is that we have not updated WildFly Core to the management API used by WildFly 31. This will be done at https://issues.redhat.com/browse/WFCORE-6620, we plan to release it this Wednesday at most. |
@yersan I see, thank you very much for explanation and for looking at my HostExcludesTestCase changes! |
@@ -53,6 +53,7 @@ public abstract class LayersTestBase { | |||
"org.hornetq.client", | |||
// TODO we need to add an xts layer | |||
"org.jboss.as.xts", | |||
"org.wildfly.extension.elytron.jaas-realm", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR has needed more additions but in general could it be useful if the LatestTest got some of these items directly from a class in WildFly Core so when changes are made to WildFly Core we reduce the number of round trips to get something merged.
/retest |
Superseded by #17622, already merged |
https://issues.redhat.com/browse/WFLY-18163
This PR is required so that the CI on wildfly/wildfly-core#5587 passes
This is a feature https://issues.redhat.com/browse/WFLY-18163