I just upgraded my gradle plugin and suddenly the builds broke because 
of this pull request:
https://github.com/jenkinsci/gradle-plugin/pull/12

I had my gradle.properties file with the repository information in my 
build user's .gradle directory and it took a bit for me to figure out 
that GRADLE_USER_HOME is being set incorrectly according to [1].  The 
order is gradle.properties from the project, then gradle.properties from 
GRADLE_USER_HOME, which is ~/.gradle by default, then properties from 
the command line.

It appears that the gradle plugin has changed the way gradle works and 
has taken a default that is different than gradle's default.  I would 
not expect the plugin to have different defaults than the actual tool, 
it leads to confusion when things don't work like is documented online.

I know I can override the GRADLE_USER_HOME variable with the -g switch 
and a few other methods, which is what the author of the pull request 
should have done, -g $WORKSPACE.

Am I being too nit picky?  Has the time for complaining passed since 
this happened 4 months ago?  I just wanted to get a feel for what the 
community felt and see if I am alone on my thoughts about this. But its 
like the git plugin suddenly changed and now if you leave branches blank 
it only checks master instead of all branches.


[1] - http://www.gradle.org/docs/current/userguide/build_environment.html

Will

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to