Publishing on Quarkus Registry

[mcollovati]

Quarkus provides an extension registry where also non-platform extensions can be published, and the easily discovered by browsing the dedicate web page or using developer tools.

Quarkus also provides a web tool, similar to start.vaadin.com, that allows to quickly set up an application by selecting the needed extension from the list of artifacts published on the registry.

The publishing process seems straightforward, and it should be done only once. After that, a scheduled job will check Maven Central for new versions and update the Quarkus Extension Registry

[mcollovati]

Direct link to the Quarkus Ecosystem CI README, with instructions to setup a Github Action to validate the extension at every Quarkus release

[mcollovati]

For the automatic builds against the latest Quarkus version, it seems like it is possible to define different target branches in the metadata with the alternatives key, as in the following example

https://github.com/quarkusio/quarkus-ecosystem-ci/blob/6618e668d099695dd93ffef673a07c38373181c5/kogito-quarkus/info.yaml#L1-L8

Then the github action can use the environment variable ALTERNATIVE when running the ./ecosystem-ci/setup-and-test script

https://github.com/kiegroup/kogito-runtimes/blob/5c494b0be92803cab7a01fd6e345e21c45969160/.github/workflows/nightly-quarkus-ecosystem.yaml#L101-L106

[gastaldi]

Welcome aboard!