Disable Gradle daemon for Java interop test building

We have seen an issue where `rm -r "$HOME/.gradle"` fails because
"Directory not empty". It seems likely this is due the fact Gradle is
still running in daemon form. The build script doesn't get any advantage
by running the daemon, so we just disable it.

Fixes #20423
pull/20455/head
Eric Anderson 6 years ago
parent 42979d3db1
commit 05c603729e
  1. 2
      templates/tools/dockerfile/java_build_interop.sh.include
  2. 2
      tools/dockerfile/interoptest/grpc_interop_java/build_interop.sh

@ -22,7 +22,7 @@ cp -r /var/local/jenkins/grpc-java /tmp/grpc-java
cp -r /var/local/jenkins/service_account $HOME || true
pushd /tmp/grpc-java
./gradlew :grpc-interop-testing:installDist -PskipCodegen=true
./gradlew --no-daemon :grpc-interop-testing:installDist -PskipCodegen=true
mkdir -p /var/local/git/grpc-java/
cp -r --parents -t /var/local/git/grpc-java/ ${'\\'}

@ -22,7 +22,7 @@ cp -r /var/local/jenkins/grpc-java /tmp/grpc-java
cp -r /var/local/jenkins/service_account $HOME || true
pushd /tmp/grpc-java
./gradlew :grpc-interop-testing:installDist -PskipCodegen=true
./gradlew --no-daemon :grpc-interop-testing:installDist -PskipCodegen=true
mkdir -p /var/local/git/grpc-java/
cp -r --parents -t /var/local/git/grpc-java/ \

Loading…
Cancel
Save