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

Gradle Plugin seems to change gradlew

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • gradle-plugin
    • None
    • Cloudbees Jenkins; Gradle Plugin Version 1.22

      When I configure a job to use the gradlewrapper gradlew gets changed (and possibly a bunch of directories created).

      This is a problem at least to me, since I'd like to use the job for releasing and the release plugin checks that the workingcopy is unmodified (which I can disable, but which is actually a useful and important feature to get reproducable builds)

      Here is a stackoverflow question, created by myself regarding the issue ( http://stackoverflow.com/q/15847518/66686 ):

      The plugin starts by checking if my working copy is clean, so that only properly versioned stuff gets released.

      This works just fine on my local machine. But when I try the same thing in a Jenkins job, the build fails complaining various stuff is changed in the workplace. I decided that a lot of stuff was just internally used by jenkins and added it to `gitignore`:

      caches/
      native/
      wrapper/

      But it also considers `gradlew` as changed:

      FAILURE: Build failed with an exception.

      • What went wrong:
        Execution failed for task ':checkCommitNeeded'.
        > You have uncommitted files:
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        M gradlew
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

            gbois Gregory Boissinot
            schauder Jens Schauder
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: