Publish quarkus-openshift-test-suite library to maven repo

[llowinge]

Camel Quarkus would like to consume your common/app-metadata library. Would be possible to do releases ?

[rsvoboda]

We are working on product counterpart of Quarkus at the moment and thus we won't be able to work on this in foreseeable future.

Qaurkus QE team wants to invite you for closer cooperation on this project. We need to work closely on this topic as your (and your project/product) requirements and expectations can slightly differ comparing to our needs.

We are open to proposal from your side as you can help us to define the sharable parts of this testsuite.
One thing to be aware of is that this TS was not primarily designed as a framework.
On the other hand it was still quite a high priority to keep things properly separated.

[Ladicek]

For the record, when I forked the test framework from this test suite into Thorntail (https://github.com/thorntail/openshift-test/), I got rid of the app-metadata stuff (because there's obviously nothing like that in Thorntail) and replaced it with a more general mechanism: the test framework reads the openshift.yml file and discovers all the metadata from there. That has one consequence: there can be multiple applications in the file. (Similarly, I made the @CustomAppMetadata annotation repeatable.) The test framework treats the case of a single application in a special way (e.g. if there's single application, RestAssured is configured to point to it), but it also allows working with multiple easily.

[rsvoboda]

So you are expecting that openshift.yml is properly generated. I know there are some issues with openshift.yml here and there, but the main properties we care about are imho stable.

Benefit of app-metadata module to me is that it's nice example of custom extension and it helps us to reveal issues in this are, mainly product dependency issue. So not convinced we should get rid of it.

About multiple applications in the file - you have handcrafted openshift.yml file? of there is some support for it as part of Thorntail, or even in Dekorate?

[rsvoboda]

Some resources related to publishing (I prefer GH Action based solution if possible):

• https://docs.github.com/en/actions/guides/publishing-java-packages-with-maven
• https://blog.frankel.ch/github-actions-maven-releases/
• https://github.com/quarkiverse/quarkus-github-api/tree/master/.github/workflows

[Ladicek]

So you are expecting that openshift.yml is properly generated. I know there are some issues with openshift.yml here and there, but the main properties we care about are imho stable.

Indeed I do. I think we assume the same in this test suite as well, at least to a certain degree.

Benefit of app-metadata module to me is that it's nice example of custom extension and it helps us to reveal issues in this are, mainly product dependency issue. So not convinced we should get rid of it.

I totally agree it's a nice example of an external extension, but I'm not sure if that's the purpose of this test suite. But, yea, I agree that custom extensions need to be tested in one way or another, and I don't mind app-metadata being the canary in the coal mine for now :-)

About multiple applications in the file - you have handcrafted openshift.yml file? of there is some support for it as part of Thorntail, or even in Dekorate?

That is supported in Fabric8 Maven plugin, JKube, and Quarkus as well (src/main/kubernetes for example). Not sure about Dekorate specifically.

[llowinge]

I like the idea about removing app-metadata and having it automated based on openshift.yml but with possibility of @ CustomAppMetadata`.

[rsvoboda]

We are working on new library for usage against various environments.

We have first release available - https://github.com/quarkus-qe/quarkus-test-framework/releases/tag/0.0.1

Resources to be checked:

• https://github.com/quarkus-qe/quarkus-test-framework/blob/main/README.md
• https://github.com/quarkus-qe/quarkus-test-framework/tree/main/examples
• https://github.com/quarkus-qe/quarkus-test-suite

@llowinge / @Ladicek please check it out, your input will be appreciated.