There was a feature request to enable build outcome caching tools such as Gradle Enterprise Build Cache (that works for Maven as well) to be able to cache outcomes of `quarkus:build` goal. This is especially relevant for native builds.

The way these build caching tools work is they track input to Maven goals and record their outcomes. On the next build they check whether the inputs have changed and if they haven't they may pull the outcome from previous builds and skip execution of the corresponding goals in the current build.

Caching outcomes of `quarkus:build` is not as straightforward due to the fact that Quarkus config is a hierarchy of various config sources, some of which may not be static and not even explorable.

Collaborating with the Gradle Enterprise team, I opened this PR https://github.com/quarkusio/quarkus/pull/34713 that enables recording and tracking build time config changes between builds.

I am suggesting to backport this feature to the 3.2 stream to enable our customers who use build outcome caching tools to also cache outcomes of `quarkus:build`.