If I understood correctly both use cases are exactly the same. Gradle Wrapper provides further features such as:
- task inde, as you can see in the left side - console output colourful - besides of that it does also use the Gradle installation approach, so you can either have the gradle wrapper approach or the gradle version approach and those versions are configured in the global setup. - OS agnostic Cheers On Monday, 18 January 2016 02:12:06 UTC, David Karr wrote: > > If I have a Gradle build that uses the Gradle Wrapper, I'm assuming that > if I have Jenkins using the Jenkins Gradle plugin and the "Use Gradle > Wrapper" checkbox is set for the job, then Jenkins will just execute the > Gradle Wrapper script stored in the project. Is this correct? > > What exactly are the advantages of doing this, as opposed to just having a > dumb Jenkins job execute "./gradlew"? > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8e8db437-c6e2-43a8-b166-ef67d657f193%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
