-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure DevOps Build_JDK11_Linux Job build should set PATH for java 11 instead of 8 binary to be used #2012
Comments
So looking at https://github.com/quarkusio/quarkus/blob/master/azure-pipelines.yml, we see ... via https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/maven we can find https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks/MavenV3 ... if I understand that doc correctly, and it really works like described, then because A regular PS: This is an ugly workaround which ideally should not be needed at all - I've therefore opened an issue for a future (probably MUCH later?) real solution: microsoft/azure-pipelines-tasks#10103. |
Duh; I'm stupid - I can just do that in (Java) code, of course. Incl. catering for if there is no JAVA_HOME set. |
…rkusio#2012) This should fix the test failure on environments where the wrong `java` is on the `PATH`, such as in Azure; for details, see microsoft/azure-pipelines-tasks#10103.
…rkusio#2012) This should fix the test failure on environments where the wrong `java` is on the `PATH`, such as in Azure; for details, see microsoft/azure-pipelines-tasks#10103.
I've successfully worked around this in the proposed new Leaving this issue open only as a reminder that the |
…rkusio#2012) This should fix the test failure on environments where the wrong `java` is on the `PATH`, such as in Azure; for details, see microsoft/azure-pipelines-tasks#10103.
#1986 is passing the Windows_Build Job (which, presumably is Java 8?) but fails in the Build_JDK11_Linux Job due to what I suspect is a configuration issue of a detail of how the CI jobs are set up - and which could affect other similar tests like what #1986 does in the future as well (e.g. this will likely also affect #2005):
Basically what #1986 does is that it builds a test app Quarkus JAR - using Maven which calls Gradle. Both of these (seem to) run under Java 11 - as they should, for that job; so far, all good. Now the (new) IT of #1986 attempts to test this built JAR, by simply (literally) exec-ing
java -jar .../gradle-it-runner.jar
. Note that it doesn't pick ajava
- so whatever comes first onPATH
will run .. which seems right - a test like that one should not have to worry about Java 8 vs 11 test job environments, agreed? Now, as the full stack trace from the test failure below illustrates, it seems thatjava
onBuild_JDK11_Linux
is actually Java 8 and not Java 11 - and that's wrong.The DevOps Build_JDK11_Linux Job build should set PATH for a Java 11 instead of 8
java
binary.@stalep @cescoffier @gsmet who actually maintains that CI and can help with this?
The text was updated successfully, but these errors were encountered: