While we updated the BOM, it's able to actually determine which modules are affected by this particular BOM change (an update to the MariaDB driver) instead of building most of the tree and it only built these modules:
extensions/devservices/mariadb
extensions/reactive-mysql-client/deployment
extensions/jdbc/jdbc-mariadb/runtime
extensions/jdbc/jdbc-mariadb/deployment
integration-tests/jpa-mariadb
integration-tests/hibernate-orm-compatibility-5.6/mariadb
integration-tests/hibernate-orm-tenancy/datasource
integration-tests/hibernate-orm-tenancy/connection-resolver
integration-tests/hibernate-orm-tenancy/schema-mariadb
integration-tests/hibernate-orm-tenancy/connection-resolver-legacy-qualifiers
integration-tests/opentelemetry-jdbc-instrumentation
We might have to tweak it further (and maybe also implement the missing feature that makes us use GIB for the Quickstarts build) but it looks quite interesting to me.
And even when we use GIB for the quickstarts, it's more interesting than before as the list of artifacts we declare as modified as the input of the GIB build is a lot smaller than it used to be.
To be honest, the BOM case was the one I was the most interested in.
I will continue the experimentation until I'm reasonably confident it's safe.
--
Guillaume