+1 to using Gradle wrappers. Given how much Gradle build files can be affected by version changes, allowing the two to be out of sync is likely to have problems down the road :)
Richard. On Wed, 27 May 2015 at 00:01 corneil.duples...@gmail.com < corneil.duples...@gmail.com> wrote: > An alternate way to ensure you use a specific version of Gradle that may > not be available yet is to add the gradle wrapper to your project and to > configure the Jenkins plugin to use the wrapper. > https://docs.gradle.org/current/userguide/gradle_wrapper.html > > If you don't want the wrapper to be downloaded from the internet by your > build you can place the gradle distribution in a binary repository or on a > server in your network and set the url in the gradle-wrapper.properties. > Then you don't have to make changes to the Jenkins configuration when > upgrading in future, you just need to update the gradle-wrapper.properties. > > Regards > Corneil > > > [image: --] > Corneil du Plessis > [image: https://]about.me/corneil > <https://about.me/corneil?promo=email_sig> > > On 26 May 2015 at 13:33, Christopher Orr <ch...@orr.me.uk> wrote: > >> On 25/05/15 11:25, Carlo Lupo wrote: >> >>> We are using since some weeks Gradle version 2.4 in our build scripts. >>> But when we want upgrade the Gradle version used vai Jenkins at Jenkins' >>> system page ("install from gradle.org"), it only displays the Gradle >>> release candidates "2.4-rc-1" and "2.4-rc-2 in the combo box. Jenkins >>> obviously doesn't know from Gradle version "2.4". >>> >>> So my question is: how are the entries of this combo box updated? Is >>> Jenkins looking at "gradle.org" and does somehow not detect the latest >>> release version? How can we influence what is displayed in the combo? We >>> do not wanna see all those old versions (which are only of some historic >>> interest). >>> >> >> There is an automated process which updates these versions daily (from >> gradle.org in this case), but unfortunately that process is currently >> broken. >> >> The scripts are here: >> https://github.com/jenkinsci/backend-crawler >> >> The infrastructure bug tracking the brokenness is here: >> https://issues.jenkins-ci.org/browse/INFRA-225 >> >> Regards, >> Chris >> >> -- >> 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/55645A04.1040802%40orr.me.uk >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CACPng9a7fc6qokbhJ3e4gLi9ry8NueWwFp0_F0Bhx25YkxEs6A%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CACPng9a7fc6qokbhJ3e4gLi9ry8NueWwFp0_F0Bhx25YkxEs6A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAMui946jvzPW2e43f3VP2a4kV7kTHKyYRv786G261SWne1J14g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
