|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
The above commit is certainly the one that broke this and here is the pull request:
https://github.com/jenkinsci/gradle-plugin/pull/12
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.
Its like the git plugin suddenly changed and now if you leave branches blank
it only checks master instead of all branches.
Another workaround would be putting -g /home/[build user]/.gradle in the switches.