Open metacosm opened 1 year ago
/cc @geoand (kubernetes), @iocanel (kubernetes)
@metacosm: The tests we use to test the generation process are mostly QuarkusProdModeTest, so I am wondering if there is something in your setup that triggers it. Do you have a reproducer?
For that matter, you can see the issue with the tests for the bundle-generator/deployment in main as well.
I can't reproduce. I used the main branch but it worked fine. I also used the main branch + the code from the commit you provided.
In both cases things worked just fine.
What do you mean by "things worked fine"? You didn't get the warning or did the tests pass? Note that the exception never actually shows up: you need to debug to see it happen (or change the code in a way similar to https://github.com/quarkusio/quarkus/pull/36057) so the only thing that should be "wrong" with main or the commit would be that the kubernetes manifests are not generated, the warning shows up but the tests are passing because they currently avoid testing things where things actually fails because the kubernetes manifests are not properly generated.
Describe the bug
I'm seeing the following error message when running my tests from maven: 2023-09-20 14:19:44,884 WARN [io.qua.kub.dep.KubernetesProcessor] (build-5) No project was detected, skipping generation of kubernetes manifests!
Adding additional information to Quarkus itself, the issue seems to come from dekorate:
Of note, this only occurs when running the tests from my typical maven build. If I run the tests from my IDE (to debug them, for example), then everything works as expected.
Expected behavior
Tests should behave the same way wherever they are executed.
Actual behavior
Kubernetes manifests are not generated when they should really be.
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.2.6.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response