Skip to content
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

Use latest RHBK in nightly pipelines #497

Open
trepel opened this issue Jul 24, 2024 · 4 comments
Open

Use latest RHBK in nightly pipelines #497

trepel opened this issue Jul 24, 2024 · 4 comments

Comments

@trepel
Copy link
Contributor

trepel commented Jul 24, 2024

Summary

Use latest RHBK (Red Hat Build of Keycloak) in nightly pipelines to test the Authorino integration with Keycloak.

There are already some resources for RHBK deployment in our tools repo (probably would require some changes to work with the Kuadrant testsuite)

@averevki
Copy link
Contributor

I think this issue belongs under the testsuite repo. Pipelines have nothing to do with cluster environment for testsuite. Feel free to assign me 👍

@trepel
Copy link
Contributor Author

trepel commented Jul 25, 2024

@averevki Hmm, to be honest I did not think much about it when creating this issue but thinking about it now, testsuite should not be responsible for setting up cluster, kuadrant, tools etc. Testsuite expects all this to be in place before it is triggered, no?

In my mind we aim for pipeline capable of creating a cluster, installing kuadrant with all the dependencies and configuring it, installing tools and other dependencies of the test suite, triggering testsuite, reporting results, cleanup.

@averevki
Copy link
Contributor

@averevki Hmm, to be honest I did not think much about it when creating this issue but thinking about it now, testsuite should not be responsible for setting up cluster, kuadrant, tools etc. Testsuite expects all this to be in place before it is triggered, no?

You are correct, but with tools it doesn't matter what tools there are. They are all, essentially, installed with one command and the issue here would be to make tools compatible with the testsuite. We had some problems with the deployment of different keycloak providers before, some of them use different credentials secret naming, realms and users which are created during tests can have different requirements, the way each of them setup tls, etc.

In my mind we aim for pipeline capable of creating a cluster, installing kuadrant with all the dependencies and configuring it, installing tools and other dependencies of the test suite, triggering testsuite, reporting results, cleanup.

I guess the nightly pipeline mentions misled me. I believe we have never talked about the new cluster provisioning pipelines, for now. We should create an epic for this.

@trepel
Copy link
Contributor Author

trepel commented Jul 26, 2024

Thanks for explanation. I will transfer the issue as you suggested.

I guess the nightly pipeline mentions misled me. I believe we have never talked about the new cluster provisioning pipelines, for now. We should create an epic for this.

You're right that this would probably warrants an Epic. So far I just created issues related to cluster provisioning recently.

@trepel trepel transferred this issue from Kuadrant/testsuite-pipelines Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants