Quarkus Maven Plugin behaviour in Gitlab CI - Gitlab CI breaks the Quarkus Maven Plugin? #23685
-
Hi all, I have searched quite a bit, but haven't found an answer, so I have to ask here. TL;DR: Gitlab CI / gitlab runner breaks the quarkus maven plugin... how can that be? Here's the situation - we're building (trying to build) an application using GitLab CI with the gitlab runner on Kubernetes (OpenShift 4.8). The
So, it spins up a container with The weird first error we hit was
and trying to switch off the banner (why would it complain about this in the first place) via Now we're hitting the next one:
If you look at the stacktraces, it seems to be somehow file access related...
We're a bit at a loss here - one of our colleagues also tried to run the maven command in a container created from this image and there it built as it should.... Anyone seen anything like this before? Thanks, Markus |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
I can reproduce the 'URI has a query component' part by building on a path with a '?' in it. |
Beta Was this translation helpful? Give feedback.
-
nice one @stuartwdouglas - #23696
in the pod. when i run this in the runner pod, you can see home is "?"
the reason we dont see this on other java apps (like the one i tried above) is because the the other workaround is to set the mvn option |
Beta Was this translation helpful? Give feedback.
-
Same issue encountered on the company's Jenkins building in a container, and setting -Duser.home is a working workaround. This workaround was not needed on 2.6.1, but started being needed on 2.7.0, 2.7.1 and 2.7.2 so far. So #23696 did not fix it in 2.7.2.Final (just tried). |
Beta Was this translation helpful? Give feedback.
nice one @stuartwdouglas - #23696
i debugged further. i think this happens because the gitlab runner fires up with a certain securityContext which end up as
in the pod. when i run this in the runner pod, you can see home is "?"
the reason we dont see this on other java apps (like the one i tried above) is because the
io.quarkus.vertx.http.deployment.StaticResour…