-
Notifications
You must be signed in to change notification settings - Fork 75
Task :nodeSetup fails #124
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
Comments
I wasn't ignoring it, I just never got any response from the reporter to help me troubleshoot the issue. I suppose I should go ahead and close it, since it's been open so long. I'm (still) not really familiar with this plugin. Interestingly, a simple setup fails for me locally with the same HTTP 404 (Resource missing. [HTTP GET: https://nodejs.org/dist/v12.13.1/ivy.xml]). build.gradle.kts group = "com.github.keeganwitt.tests"
version = "1.0.0-SNAPSHOT"
plugins {
id("com.moowork.node") version "1.3.1"
}
node {
version = "12.13.1"
distBaseUrl = "https://nodejs.org/dist"
download = true
workDir = file("${project.buildDir}/nodejs")
nodeModulesDir = file("${project.projectDir}")
} settings.gradle.kts rootProject.name = "gradle-node"
However, I don't think there's an issue with the Docker image or the network configuration, because I can curl the URL just fine |
It looks like it is able to make a connection to the server and pull the certificate and cipher suites in too. I'm not sure what's going on here.
|
Actually, the curl didn't succeed, the curl was pulling in a 404 HTML response. Looking in the parent directory (https://nodejs.org/dist/v12.13.1/), I don't see that Ivy XML file there anymore. Perhaps Node doesn't publish artifacts as an Ivy repo anymore? It sounded like from some of the comments in GitHub that the ivy.xml was a fallback that appears to have not been working for several versions. You might find this useful (if you haven't seen them already): srs/gradle-node-plugin#292 (comment) (commenter says Gradle 6 doesn't work, but Gradle 4 does). From the issue mentioned in that comment, they mentioned a fork of the plugin (https://github.com/node-gradle/gradle-node-plugin). When I switched to the fork, it worked for me. |
Interestingly enough my fried suggested me to simply run the npm tasks with the |
Running with gradlew won't use the Gradle provided by the image, it will use whatever version your wrapper is configured to use. There shouldn't be any difference though, all this image is is an unzipped Gradle archive on top of the official AdoptOpenJDK base image (with gradle tossed into the path). The advantage to using this image to to avoid downloading Gradle each time (which the wrapper will do unless you mount the directory Gradle is downloaded into somewhere so it can be persisted). I'd suggest maybe trying that same version your wrapper uses. Or if you're happy with the wrapper, you could use one of the Java base images (AdoptOpenJDK, Amazon Corretto, OpenJDK, etc) instead of this image, to save some disk space, since you aren't using the Gradle in the image. At the moment, it seems to me this is likely an issue with that plugin and its compatibility with different Gradle versions, and not an issue with this Docker image. |
I'm aware of #88 but the issue seems to be closed/ignored.
Running
gradle appInstall --info
gives me the following error:The location the task has been looking for:
https://nodejs.org/dist/v12.12.0/ivy.xml
returns a 404 error.My
build.gradle.kts
:Running the build locally works. I checked my version which is
5.1
so I tried to change the docker tag to5.1.1-jdk-slim
. It didn't work and I wasn't expecting it because the error message doesn't look like it's version specificAny help would be appreciated!
The text was updated successfully, but these errors were encountered: