[JIRA] (JENKINS-15166) Gradle plugin falis to save selected Gradle Version in Project configuration

Mon, 17 Sep 2012 15:59:53 -0700

Sean Ford commented on Bug JENKINS-15166

Nice, I was just coming here to report the same bug. I had problems with Gradle plugin version 1.19 and Jenkins version 1.481. Reverting the Gradle plugin back to version 1.16 fixed the problem for me.

I did some digging on this and it seams that the <gradleName/> property isn't being saved into a job's config.xml file. Example:

...
  <builders>
    <hudson.plugins.gradle.Gradle>
      <description></description>
      <switches></switches>
      <tasks>clean test</tasks>
      <rootBuildScriptDir></rootBuildScriptDir>

<!-- <gradleName>YOUR_GRADLE_NAME</gradleName> should appear here -->

      <buildFile></buildFile>
      <useWrapper>false</useWrapper>
    </hudson.plugins.gradle.Gradle>
  </builders>
...

For a work-around, you can add <gradleName>YOUR_GRADLE_NAME</gradleName> to your project's config.xml and then have Jenkins "Reload Configuration from Disk". This will fix gradle until you re-save the job's config.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to