Conditionally run Quarkus IT in GHA based on code changes #29118
Assignees
Labels
area/dist/quarkus
area/testsuite
Indicates an issue on the Testsuite area
kind/enhancement
Categorizes a PR related to an enhancement
release/25.0.0
team/cloud-native
team/continuous-testing
Comments
vmuzikar
added
area/testsuite
2 tasks
vmuzikar
changed the title
vmuzikar
added a commit
to vmuzikar/keycloak
that referenced
this issue
Apr 29, 2024
Closes keycloak#29118 Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
vmuzikar
added a commit
to vmuzikar/keycloak
that referenced
this issue
Apr 29, 2024
Closes keycloak#29118 Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
vmuzikar
added a commit
to vmuzikar/keycloak
that referenced
this issue
May 3, 2024
Closes keycloak#29118 Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
vmuzikar
added a commit
that referenced
this issue
May 7, 2024
Closes #29118 Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We should not need to run the Quarkus testsuite with each PR. Full testsuite needs to be executed only when code is changed in the
quarkusmodule, or when the rootpom.xmlchanges. This change should be safe enough. We run the base integration testsuite with Quarkus, so any code change in core Keycloak code base that breaks the Quarkus integration should be visible there.Full testsuite should still run nightly in case something slips between the cracks.
Discussion
No response
Motivation
No response
Details
No response
The text was updated successfully, but these errors were encountered: