What does "Use Gradle Wrapper" do in Jenkins Gradle plugin?

[David Karr]

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"?

[Victor Martinez]

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

[David M. Karr]

On 01/18/2016 02:12 AM, Victor Martinez wrote:

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

I'm having trouble understanding much of this.  I don't understand what "task inde" means, or a reference to the "left side".  Is this a benefit of  the Jenkins Gradle plugin?  You seem to be saying that  this is a list of benefits of the "Gradle Wrapper", when I think you mean to say they are benefits of the Jenkins Gradle plugin.

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 jenkinsci-use...@googlegroups.com.
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.

[Daniel Beck]

On 18.01.2016, at 18:14, David M. Karr <davidmic...@gmail.com> wrote:

> I don't understand what "task inde" means, or a reference to the "left side".

When you view the build log, the Gradle Plugin adds an index to the left side (below the sidepanel links) that lets you jump directly to the tasks.

[Victor Martinez]

Thanks Daniel, I did typo in my previous enumeration. as David spotted it was related to the Gradle Plugin rather than the gradle wrapper option within the gradle plugin itself. IMO, those are one of the keys features and might help you to avoid using the ./gradlew shell/batch command in any jenkins job.