Make Quarkus Maven/Gradle plugins compatible with Develocity test distribution #50602

oehme · 2025-10-16T18:08:32Z

Develocity's test distribution feature allows distributing Gradle/Maven tests on remote machines. To do so, it needs to:

Know all the inputs of the test, so it can transfer them to the remote machine
Replace any file paths (e.g. in system properties or configuration files) with the corresponding paths on the remote machine

This PR makes Quarkus compatible with these requirements. It changes the serialized application model to a textual format (JSON), so that Develocity can easily find and replace file paths inside it. Additionally, it exposes the deployment dependencies as a Maven project property, because those were otherwise not visible. In the Gradle plugin, they were already provided as a separate dependency Configuration.

I've opted for Jackson as the serialization library, because it is very flexible and allowed me to adapt to the ApplicationModel with minimal changes to the model classes.

After these changes and some minor tweaks on the Develocity side, I was able to successfully run the quarkus-super-heroes example project with test distribution.

aloubyansky · 2025-10-16T19:39:53Z

Thanks @oehme! Do you think we could keep the Jackson JSON binding in a separate module, out of the appmodel artifact? E.g. quarkus-appmodel-json or something? There are some basic API classes from which we probably don't want to link to Jackson API (such as Artifact*, PathTree, etc).

oehme · 2025-10-17T09:51:57Z

Do you think we could keep the Jackson JSON binding in a separate module, out of the appmodel artifact? E.g. quarkus-appmodel-json or something?

If I can't depend on Jackson in the appmodel project, then I can't use the binding annotations. This would mean writing a bunch of manual serialization/deserialization code to handle all the different types and polymorphism. And then everyone who currently uses BootstrapUtils would have to add a dependency on this new appmodel-json project anyway, so it doesn't really improve anything as far as I can see. So in my opinion, not a realistic/worthwhile option.

oehme · 2025-10-21T12:39:01Z

Fixed the formatting issue above.

oehme · 2025-10-22T16:10:32Z

The failures above are probably due to a merge conflict, I'll fix those up.

This allows Develocity to auomatically replace the file paths in this model when running tests on a remote machine, where the paths are different than locally. We use jackson, because it has the necessary flexibility to handle the application model with its deep nesting and various subclasses without having to make many changes to the model itself.

In order to run tests on remote agents, Develocity needs to know all files necessary to run the tests, as well as the application under test. The deploy classpath contains dependencies that are not part of the regular Maven project model and we need to expose it in some way that Develocity can easily grab and track it.

oehme · 2025-10-27T17:34:02Z

This should be passing now.

quarkus-bot · 2025-10-28T18:51:14Z

Status for workflow `Quarkus CI`

This is the status report for running Quarkus CI on commit 823022f.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging/deployment

❌ io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

Expecting actual: ["-6","-7","-8","-10","-11","-12","-13","-14"] to start with: ["-6", "-7", "-8", "-9"] - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual:
  ["-6","-7","-8","-10","-11","-12","-13","-14"]
to start with:
  ["-6", "-7", "-8", "-9"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:41)

⚙️ JVM Tests - JDK 21

📦 test-framework/jacoco/runtime

❌ io.quarkus.jacoco.runtime.DataFileWatchTest.waitForDataFileThatNeverAppears - History

Expecting value to be false but was true - org.opentest4j.AssertionFailedError

org.opentest4j.AssertionFailedError: 

Expecting value to be false but was true
	at io.quarkus.jacoco.runtime.DataFileWatchTest.waitForDataFileThatNeverAppears(DataFileWatchTest.java:208)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)

⚙️ MicroProfile TCKs Tests

📦 tcks/microprofile-lra

❌ org.eclipse.microprofile.lra.tck.TckRecoveryTests.testCancelWhenParticipantIsUnavailable - History

Expecting the metric Compensated callback was called Expected: a value equal to or greater than <1> but: <0> was less than <1> - java.lang.AssertionError

java.lang.AssertionError: 
Expecting the metric Compensated callback was called
Expected: a value equal to or greater than <1>
     but: <0> was less than <1>
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.eclipse.microprofile.lra.tck.TckRecoveryTests.assertMetricCallbackCalled(TckRecoveryTests.java:210)
	at org.eclipse.microprofile.lra.tck.TckRecoveryTests.testCancelWhenParticipantIsUnavailable(TckRecoveryTests.java:195)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

oehme · 2025-10-30T13:07:05Z

All green :) The flaky tests look like the same as on the mainline branch.

gsmet · 2025-10-30T13:52:49Z

independent-projects/bootstrap/app-model/pom.xml

+        <dependency>
+            <groupId>com.fasterxml.jackson.core</groupId>
+            <artifactId>jackson-databind</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>com.fasterxml.jackson.module</groupId>
+            <artifactId>jackson-module-parameter-names</artifactId>
+        </dependency>


I understand your position but I'm really not excited about this part. That means Jackson Databind will be around in the test classpath for all Quarkus apps.

It seems problematic to me. Especially for a feature that is not really core to Quarkus.

I'm not sure if we could somehow externalize this? Maybe adding an additional test artifact for this support would be acceptable?

I haven't looked into it yet but I thought we could check what it would mean to provide the binding in a separate artifact. It would still have to be added in many places though.

So if I understand you correctly, you'd like this to be an optional feature and maintain the java serialization as the default? That's possible of course. I didn't do that, since on Slack we had originally agreed on JSON as the only format.

@oehme we need to agree on the JSON binding impl library suitable for core. We had a discussion before but we need to conclude it #dev > JSON dependency in the core deployment?

I see, so no action needed from my side at this point?

Yes, let's clarify that before making further efforts. Thanks.

Have you made a decision on the JSON library?

Unfortunately, no. Sorry for the delay. I'll look into this this week.

fabricepipart1a · 2025-11-28T16:10:56Z

Hi there !
Do you have any update on this matter. Amadeus (the company I work for) is very interested to have that feature. We contemplate huge gains to accelerate our builds that spend most of their time running QuarkusTests. Is there anything blocking the progress?

aloubyansky · 2025-11-28T18:56:39Z

I do have some updates. I have a branch where I'm investigating an alternative serialization/deserialization. The basics seem to be working. I need to test it more properly, which is a work in progress.

fabricepipart1a · 2025-12-04T14:10:04Z

Lovely. Thanks for the update!

aloubyansky · 2025-12-05T16:10:49Z

I opened #51430 for a review and further discussion.
It doesn't include a couple of project properties set in the mojo in this PR. That could be a separate PR and discussion.

oehme · 2025-12-05T17:11:32Z

I'll rework this PR to just do those changes, because they'll also be necessary for test distribution.

Thank you so much for your other PR!

quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle area/maven labels Oct 16, 2025

This comment has been minimized.

Sign in to view

oehme force-pushed the oehme/json-appmodel branch from b0ca678 to d8ed192 Compare October 17, 2025 10:45

This comment has been minimized.

Sign in to view

oehme force-pushed the oehme/json-appmodel branch from d8ed192 to 2270268 Compare October 21, 2025 12:38

This comment has been minimized.

Sign in to view

quarkus-bot bot added the triage/flaky-test label Oct 21, 2025

oehme added 2 commits October 22, 2025 20:49

oehme force-pushed the oehme/json-appmodel branch from 2270268 to 823022f Compare October 22, 2025 20:57

gsmet reviewed Oct 30, 2025

View reviewed changes

aloubyansky mentioned this pull request Dec 5, 2025

(De)Serialize ApplicationModel (from) to JSON instead of Java Object Serialization #51430

Open

Make Quarkus Maven/Gradle plugins compatible with Develocity test distribution #50602

Are you sure you want to change the base?

Make Quarkus Maven/Gradle plugins compatible with Develocity test distribution #50602

Conversation

oehme commented Oct 16, 2025

Uh oh!

aloubyansky commented Oct 16, 2025

Uh oh!

This comment has been minimized.

oehme commented Oct 17, 2025

Uh oh!

This comment has been minimized.

oehme commented Oct 21, 2025

Uh oh!

This comment has been minimized.

oehme commented Oct 22, 2025

Uh oh!

oehme commented Oct 27, 2025

Uh oh!

quarkus-bot bot commented Oct 28, 2025 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Status for workflow Quarkus CI

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging/deployment

⚙️ JVM Tests - JDK 21

📦 test-framework/jacoco/runtime

⚙️ MicroProfile TCKs Tests

📦 tcks/microprofile-lra

Uh oh!

oehme commented Oct 30, 2025

Uh oh!

gsmet Oct 30, 2025

Choose a reason for hiding this comment

Uh oh!

aloubyansky Oct 30, 2025

Choose a reason for hiding this comment

Uh oh!

oehme Oct 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aloubyansky Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

oehme Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

aloubyansky Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

oehme Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

aloubyansky Nov 24, 2025

Choose a reason for hiding this comment

Uh oh!

fabricepipart1a commented Nov 28, 2025

Uh oh!

aloubyansky commented Nov 28, 2025

Uh oh!

fabricepipart1a commented Dec 4, 2025

Uh oh!

aloubyansky commented Dec 5, 2025

Uh oh!

oehme commented Dec 5, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

quarkus-bot bot commented Oct 28, 2025 •

edited by github-actions bot

Loading

Status for workflow `Quarkus CI`

oehme Oct 31, 2025 •

edited

Loading