This message was deleted.

Please do not split topics across several threads. This makes following the conversation in the threads view very hard as the context of the other messages is missing. If you have additional information either edit the original message or post to its thread. Regarding the problem, well the error tells you most likely that you use the

com.moowork.node

with a Gradle version it is not compatible with (i.e. 6+) and that you should replace it with the

com.github.node-gradle.node

plugin.

I updated it and ran but got below warning.

yes, those are security warnings that you will need to decide how to action.

it is getting stuck

It is first of all no longer a Gradle topic. 🙂

I am pasting my build file

Is there a Gradle question hidden somewhere?

node {
    download = true
    version = "9.11.1"

https://github.com/nodejs/release#release-schedule End of life: 2018-06-30

npmVersion = "5.6.0"

https://github.com/npm/cli/releases/tag/v5.6.0 Tagged Nov 28, 2017 That's not just "old" at that point… (I otherwise agree with Vampire it's no longer Gradle-related)

npm_build is getting failed while using build.gradle file. I am attaching the build.gradle file. Kindly help me to get npm build command.

This is a Node issue (most likely something to do with the tools your Node build is using: webpack? whatever) You should ask on StackOverflow or a Node (or whatever is actually failing) community. But be prepared to be told to update your build first.

moch is used

This is still not the least Gradle releated.

ok no problem

Or if it is, you miss to tell us how.

npm run build command is getting executed when I run from command line

You still did not share any error message

ok thanks let me try

Run with

--info

or

--debug

and / or

--scan

to get more information on what is happening

jenkins@ip-172-31-2-76:~/workspace/TrainAvailability_main$ ./gradlew npm_build --info Initialized native services in: /var/lib/jenkins/.gradle/native Initialized jansi services in: /var/lib/jenkins/.gradle/native Removing 0 daemon stop events from registry Starting a Gradle Daemon, 1 busy Daemon could not be reused, use --status for details Starting process 'Gradle build daemon'. Working directory: /var/lib/jenkins/.gradle/daemon/7.4.2 Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.base/java.nio.charset=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xms256m -Xmx512m -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /var/lib/jenkins/.gradle/wrapper/dists/gradle-7.4.2-bin/48ivgl02cpt2ed3fh9dbalvx8/gradle-7.4.2/lib/gradle-launcher-7.4.2.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 7.4.2 Successfully started process 'Gradle build daemon' An attempt to start the daemon took 2.953 secs. The client will now receive all logging from the daemon (pid: 1646). The daemon log file: /var/lib/jenkins/.gradle/daemon/7.4.2/daemon-1646.out.log Starting build in new daemon [memory: 494.9 MiB] Using 1 worker leases. Watching the file system is configured to be enabled if available Now considering [/var/lib/jenkins/workspace/TrainAvailability_main] as hierarchies to watch File system watching is active Starting Build Settings evaluated using settings file '/var/lib/jenkins/workspace/TrainAvailability_main/settings.gradle'. Projects loaded. Root project using build file '/var/lib/jenkins/workspace/TrainAvailability_main/build.gradle'. Included projects: [root project 'cicd-pipeline-train-schedule-jenkins']

Configure project :

Evaluating root project 'cicd-pipeline-train-schedule-jenkins' using build file '/var/lib/jenkins/workspace/TrainAvailability_main/build.gradle'. Compiling build file '/var/lib/jenkins/workspace/TrainAvailability_main/build.gradle' using SubsetScriptTransformer. <-------------> 0% CONFIGURING [1m 39s]

root project > Compiling build file 'build.gradle'

If it needs long at that point, maybe your build agent is just too occupied, either CPU- or RAM-wise?

I am using Amazon Ec2 linux instance t2 micro. Could you please share me how much GB or CPU utilization required for standard execution of gradle build.

There is no "standard", heavily depends on the actual build

As much as it needs? You know your build - size the server accordingly. t2.micro instances are metered, if they run out of cpu credits they will peg at 100% cpu.

here If I run in the cloud shell it is executing perfectly. but when I try it through job it is getting stuck

compare a build

--scan

from running it in the shell vs running it in Jenkins to identify configuration differences.