Where should I put gradle.properties in Jenkins

Question

Where should I put the gradle.properties file in Jenkins?

I'm using version 1.21 of the Gradle plugin, but it isn't finding the properties file when I put it in the user home .gradle directory.

Any pointers would be much appreciated.

Thanks

UPDATED

The Gradle plugin looks by default in the workspace of each project for a gradle.properties file. In order to use one file across all jobs, you need to set your gradle home in your job configurations as follows, by adding the following under 'switches':

-Dgradle.user.home=$HOME/.gradle

Are you sure that you are putting `gradle.properties` into the correct Gradle user home? I don't think the Jenkins plugin is involved in finding it. — Peter Niederwieser, Apr 27 '13 at 06:31

score 25 · Answer 1 · answered May 02 '13 at 14:43

25

The Gradle plugin looks by default in the workspace of each project for a gradle.properties file. In order to use one file across all jobs, you need to set your gradle home in your job configurations as follows, by adding the following under 'switches':

-Dgradle.user.home=$HOME/.gradle

answered May 02 '13 at 14:43

user1740752

543
1
4
13

+1 from me! However, I'm using different nodes with different user-homes, so I configured it like -Dgradle.user.home=${GRADLE_USER_HOME} and defined the environment variable with value 'C:\Users\\.gradle' in the configuration of each node. Hope it'll help someone with similar situation as me. – P Kuijpers May 14 '18 at 14:48

score 4 · Answer 2 · answered Oct 29 '15 at 04:55

4

In your Jenkins webpage, you can see 'user.home' property in 'System Information' page. (for slve, check slave's 'System Information' page) You'd put gradle.properties under 'user.home'/.gradle/ folder and every gradle job could see that properties. Adding switch is not work if your job runs on the other slave environment (ie. Windows system)

answered Oct 29 '15 at 04:55

devmojopum

41
1

This save me for our Multi Configuration Project. That executes the same build for windows and linux – sandrozbinden May 07 '16 at 17:33

score 2 · Answer 3 · answered Mar 22 '18 at 19:01

2

In addition to the answer of @devmojopum, make sure "Force GRADLE_USER_HOME to use workspace" is not checked in your job configuration.

answered Mar 22 '18 at 19:01

user2880229

151
8

score 0 · Answer 4 · answered Feb 07 '20 at 17:18

I do not agree with the upvoted answers. This only works in single-workspace environments. If you use multiple projects, have multiple nexus environments to publish to,and want also e.g. jenkins not to mess up, then you should read

https://docs.gradle.org/current/userguide/build_environment.html

how to chain gradle properties.

Gradle project properties can be stored in a separate folder and copied to the workplace root, the latter one added to .gitignore, so everybody can configure her own passwords and settings.

This also encourages to use the FORCE flag to be uses in Jenkins.

score -6 · Answer 5 · answered Apr 24 '13 at 13:09

-6

Just put gradle.properties next to your build.gradle.

Regards, Olle

answered Apr 24 '13 at 13:09

Olle Hallin

588
1
3
12

Where should I put gradle.properties in Jenkins

5 Answers5

Linked