We just installed the Bitnami Jenkins image in our Google Cloud account. I’m very pleased with how easy it was to dive right in. But it appears there might be a misconfiguration right out of the box.
Trying to run a simple gradle build configured to use the gradle wrapper, there was a file permissions problem, namely that the tomcat user (i.e., jenkins) tried to create “/opt/bitnami/.gradle/” and stuff under it (which it doesn’t have permission to, of course). As a workaround, I ssh’d in and manually created that directory, and made it world-writable- then jenkins/gradle was able to download and unpack the wrapper-specified gradle version into it. (Another workaround might be to globally override GRADLE_OPTS as in http://jlorenzen.blogspot.com/2013/06/setting-gradle-home-directory-and-proxy.html )
Also, I don’t really want to point GRADLE_USER_HOME to the workspace directory, since then each project would have to re-download gradle into its workspace.
It seems like perhaps this workaround shouldn’t be necessary? Any insights would be appreciated!