search

quarkusio / quarkus

Quarkus: Supersonic Subatomic Java.
https://quarkus.io
Apache License 2.0
13.54k stars 2.61k forks source link

Quarkus Platform automatic release ? #32175

Open radtriste opened 1 year ago

radtriste commented 1 year ago

Description

This question came to my mind after reading https://github.com/quarkusio/quarkus/issues/31831.

As part of Kogito, we have 2 parts:

In Kogito Cloud, we use directly Kogito Runtimes for our apps but when building services, we made the choice to use the Quarkus Platform directly, for Quarkus projects (this is especially the case in Kogito Serverless Workflow which depends only on Quarkus).

But this brings sometime out of sync issues between Runtimes and Cloud parts.

We merely solved the problem on Kogito by using our own build of Quarkus Platform for our nightlies. But the problem remains on our releases as we may want to:

  1. Release our Runtimes
  2. Update Platform with our runtimes
  3. Need to update Cloud with a platform version which contains the latest runtimes reference

So I am raising the question of having automatic Platform release when a new member update its version in the Platform ?

How difficult would it be ? I am mostly seeing the case of a release after a PR is done which updates a member ...

@gsmet @aloubyansky What do you think ? cc @cristianonicolai @MarianMacik

Implementation ideas

No response

MarianMacik commented 1 year ago

From the conversation with Tristan I understood that in community a new Quarkus Platform is not released immediately after a member releases a new version of their library. So new member versions are propagated only until a new Quarkus Platform is released, that is when a new version of Quarkus is released. But in RHBQ, there are SP releases, which are build on the same version of Quarkus Platform, just a member version is updated. This would be a good addition for community as well. Is there anything holding us back with that regard?