Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35029

Gradle wrapper location should be more flexible.

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • gradle-plugin
    • None

      There have been several pull requests related to the location of the gradle wrapper. This issue is meant to concentrate the discussion for where the wrapper can be found.

      Current thinking is that the plugin should check for the wrapper in the following locations in this order:

      1. User supplied location from job cofiguration - 'Path to gradle wrapper'
      2. User supplied location from master configuration - default for all jobs on master
      3. root of build script directory - parallel to build.gradle
      4. root of workspace

      Looking for comments/discussion.

      Reference:
      https://github.com/jenkinsci/gradle-plugin/pull/9
      https://github.com/jenkinsci/gradle-plugin/pull/11
      https://github.com/jenkinsci/gradle-plugin/pull/13

          [JENKINS-35029] Gradle wrapper location should be more flexible.

          Craig Rodrigues added a comment -

          You should look at the logic in the enhanced gradle wrapper called gdub ( http://www.gdub.rocks/ )
          and see if the logic for how it looks for build.gradle can be used in what you are doing.

          Craig Rodrigues added a comment - You should look at the logic in the enhanced gradle wrapper called gdub ( http://www.gdub.rocks/ ) and see if the logic for how it looks for build.gradle can be used in what you are doing.

          Stefan Wolf added a comment -

          Fixed in 1.26 of the gradle plugin.

          Stefan Wolf added a comment - Fixed in 1.26 of the gradle plugin.

            gsimpson George Simpson
            gsimpson George Simpson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: