Open ayashjorden opened 5 months ago
@ayashjorden I'm not sure at first glance why this is failing, but I will look into it. I don't see anything wrong with what you are doing, except native_image_tool
doesn't need to be provided when you are using the new-style entrypoint (you are). It should be resolving GraalVM from Bazel Toolchains.
As for the download URL, it is valid, and so is the version tag. Bazel's mirror should be pulling from here: https://github.com/graalvm/graalvm-ce-builds/releases/download/jdk-17.0.8/graalvm-community-jdk-17.0.8_macos-x64_bin.tar.gz
I get a 404 like you do. Bazel's mirror domain isn't used directly by rules_graalvm
to my knowledge or as far as I can tell. Is that happening through a proxy or perhaps some configuration on your end?
rules_graalvm
maps its own download URLs, directly to GitHub; for example, for the version you've specified (17.0.8
):
I know Bazel's mirror maps a lot of GitHub repositories, but I am not sure if GraalVM's releases are available via their mirror.
Also, thanks for reporting, and sorry for the delay. Tag me at @sgammon to get a faster response :) tags show up in my mentions which aren't polluted by Dependabot.
(I'll preface with that probably I'm doing something wrong. although I did read through the docs.)
Our Bazel builds are going through a proxy to fetch artifacts and I am hitting a 404 when rules_graalvm tries to download the CE 17.0.8:
It seems that
graalvm-community-jdk-17.0.8_macos-x64_bin.tar.gz
does not exist onmirror-bazel-build
:https://mirror.bazel.build/github.com/graalvm/graalvm-ce-builds/releases/download/jdk-17.0.8/graalvm-community-jdk-17.0.8_macos-x64_bin.tar.gz
Configuration
WORKSPACE.bazel
:BUILD.bazel
:Thanks!