This message was deleted.
# community-supports
Slackbot
09/08/2023, 3:07 PMThis message was deleted.
a
Anze Sodja
09/08/2023, 3:13 PMIt looks like that. Our CI jobs are also failing with these errors š
r
Ryan Trontz
09/08/2023, 3:23 PMWomp womp. Do you know of any place where we can follow along on the status of this?
Ryan Trontz
09/08/2023, 3:45 PMFollow up question if you donāt mind: We run our CI builds in containers based on
eclipse-temurinv
Vampire
09/08/2023, 3:52 PMIs it in a place where toolchains are searched for?
Did you disable searching?
r
Ryan Trontz
09/08/2023, 3:58 PMHey @Vampire great questions.
Is t in a place where toolchains are searched for?Thatās a great question. When you say āitā, do you mean the installed JDK? If so, then I would assume yes since the JDK is in the default
$JAVA_HOMEDid you disable searching?Can you elaborate on this one? Did I disable what searching for what, specifically? For some additional context, we apply the foojay plugin, but we donāt do any special configuration with it currently.
Ryan Trontz
09/08/2023, 4:00 PMAh, looking at the Gradle docs, no, weāre disabling auto-detection: https://docs.gradle.org/current/userguide/toolchains.html#sub:disable_auto_detect
Ryan Trontz
09/08/2023, 4:01 PMWe generally set the toolchain version to Java 11 for all builds, and then those builds are conducted in an
eclipse-temurin:11v
Vampire
09/08/2023, 4:13 PMYeah, well, if you disable auto-detection, it can of course not be auto-detected. š
r
Ryan Trontz
09/08/2023, 4:14 PMAhhh that was just an unfortunate typo, I meant to say āno, weāre not disabling auto-detection.
v
Vampire
09/08/2023, 4:14 PMš
š¤¦āāļø 1
Vampire
09/08/2023, 4:15 PMThen maybe check what the
javaToolchainsVampire
09/08/2023, 4:16 PMIf that Java you are "missing" is the one running Gradle, it should actually also be found, no matter where it is installed. If you run Gradle with a different toolchain, then it has to be in one of the location searched by the algorithm, or configured by you
r
Ryan Trontz
09/08/2023, 4:33 PMAdded a run of the javaToolchains task to a failing CI build, and iām seeing this:
[2023-09-08T161938Z] > Task :javaToolchains
[2023-09-08T161938Z]
[2023-09-08T161938Z] + Options
[2023-09-08T161938Z] | Auto-detection: Enabled
[2023-09-08T161938Z] | Auto-download: Enabled
[2023-09-08T161938Z]
[2023-09-08T161938Z] + Eclipse Temurin JDK 11.0.19+7
[2023-09-08T161938Z] | Location: /opt/java/openjdk
[2023-09-08T161938Z] | Language Version: 11
[2023-09-08T161938Z] | Vendor: Eclipse Temurin
[2023-09-08T161938Z] | Architecture: amd64
[2023-09-08T161938Z] | Is JDK: true
[2023-09-08T161938Z] | Detected by: Current JVM
This all seems fine to me and as expected. We donāt manually set a vendor in our in our toolchain closures, just a major language version of 11.
Ryan Trontz
09/08/2023, 4:34 PMIām sorry if Iām completely missing the point here. I havenāt had to debug this before, so if Iām looking in the wrong place, Iām happy to be corrected.
v
Vampire
09/08/2023, 4:36 PMNo, seems fine. With that, it should not need to auto-provision if you only use 11 toolchain.
Maybe you can see something in the
--info--debugr
Ryan Trontz
09/08/2023, 5:35 PMWell, the debug log gave us the request, but it doesnāt seem to give a lot of insight as to why this request is being made at all:
Copy code
[2023-09-08T17:04:18Z] 2023-09-08T16:53:47.157+0000 [DEBUG] [sun.net.www.protocol.http.HttpURLConnection] sun.net.www.MessageHeader@5b1b38e46 pairs: {GET /disco/v3.0/distributions?include_versions=true&include_synonyms=true HTTP/1.1: null}{Content-Type: application/json}{User-Agent: Java/11.0.19}{Host: <http://api.foojay.io|api.foojay.io>}{Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2}{Connection: close}
[2023-09-08T17:04:18Z] 2023-09-08T16:53:47.225+0000 [DEBUG] [sun.net.www.protocol.http.HttpURLConnection] sun.net.www.MessageHeader@11385d55 pairs: {null: HTTP/1.1 503 Service Temporarily Unavailable}{Date: Fri, 08 Sep 2023 16:53:47 GMT}{Content-Type: text/html}{Content-Length: 190}{Connection: close}v
Vampire
09/08/2023, 9:25 PMWell, was worth a try. You can disable auto-provision of course. Maybe you should and see what happens. If it succeeds, then you should maybe open a bug report. If it fails, maybe the failure contains more information.
4 Views