search

quarkusio / quarkus

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

Problem with shared devservices configuration #41788

Open cj19 opened 3 months ago

cj19 commented 3 months ago

Describe the bug

I have one root project that contains multiple sub-components and i want to configure the tests to use a shared kafka container started by devservices. Every component has the application-test.properties configured like the following: quarkus.kafka.devservices.enabled=true quarkus.kafka.devservices.port=9092 quarkus.kafka.devservices.shared=true

The shared dev services which is turned on by default in the dev profile is working okay, only the test config is "misbehaving".

Expected behavior

If i set the devservices.shared property to true in applicaton-test.properties, then my expectations are there is one container running and all the running tests using the same container.

Actual behavior

If i turn on the kafka.devservices then all the components still starts their own container.

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

quarkus-bot[bot] commented 3 months ago

/cc @geoand (devservices), @radcortez (config), @stuartwdouglas (devservices)

geoand commented 3 months ago

cc @ozangunalp

Inithron commented 5 days ago

The behavior with Quarkus 3.15.1 is still the same. I am not sure if it will help but can somebody add the labe "area/kafka" because this is a kafka issue?