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

allow defining custom path to gradlew (gradle wrapper) scipt

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major Major
    • gradle-plugin
    • None
    • all

      The gradle Wrapper task creates the gradle wrapper scripts, but it does so in the project root, which sometimes is not wanted. One can override it, so that the scripts are found in, say, a 'contrib' folder, along with other helper scripts.
      Jenkins Gradle plugin has the option to use the wrapper, but it blindly tries to invoke gradlew from the project root - it is unaware of custom settings.

      Please let users define a custom path to the gradlew script within the project, or, ideally, read if somehow from the build.gradle file (it might be difficult, I aggree). Having users specify it explicitly is good enough, IMHO.

          [JENKINS-14272] allow defining custom path to gradlew (gradle wrapper) scipt

          I think a new textbox which allows to specify the gradle wrapper batch file parent would be the best solution. I would like to contribute a patch for that if there is no objection with this approach.

          Daniel Kuffner added a comment - I think a new textbox which allows to specify the gradle wrapper batch file parent would be the best solution. I would like to contribute a patch for that if there is no objection with this approach.

          Duplicate JENKINS-12769

          Daniel Kuffner added a comment - Duplicate JENKINS-12769

          Justin Ryan added a comment -

          Duplicate of JENKINS-12769. (The one without spelling mistakes)

          Justin Ryan added a comment - Duplicate of JENKINS-12769 . (The one without spelling mistakes)

            gbois Gregory Boissinot
            wujek_srujek wujek srujek
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: