I could use gradle wrapper, not used it a lot, but looking at docs I think it requires me to commit a small JAR file as part for the generated gradle wrapper files. We have a no binary files in source control policy.
So I prefer to have Jenkins set up all the tooling for me and we pull it from a local Artifactory repo. The point of the jenkins declarative pipeline is that you commit the pipeline jenkinsFile with all this alongside your source and Jenkins does the tooling side with these tools definitions. Shouldn't even need to set anything up on the Jenkins slave node (apart from a JVM for jenkins to run the slave) or have binaries in source control. For some reason the documented pipeline gradle tool DSL is not working or I have mis-configured something. Thanks, Bill On Thursday, 16 February 2017 10:00:00 UTC, Damien Coraboeuf wrote: > > Question: why can't you use the Gradle wrapper? This allows you to rely > only on a JDK. No need to rely on a Gradle installation. > > On Thursday, 16 February 2017 09:34:34 UTC+1, Bill Dennis wrote: >> >> Yes, I did all that gradle configuration. 'GRADLE_LATEST' is the label we >> used for our gradle installation. We name it that way so every time we >> update to the latest gradle, we don't need to change all our jobs that we >> want to be on the latest gradle version. We also use gradle version >> specific labels for jobs that are sensitive to the version. It shouldn't be >> a problem here. >> >> Thanks, >> Bill >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8627a815-1f39-40ea-b1ba-86b4eacc6e2a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.