[
https://issues.jenkins-ci.org/browse/JENKINS-13093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harald Schmitt updated JENKINS-13093:
-------------------------------------
Summary: Update Gradle backend-crawler to new artifacts location
(was: Add Gradle 1.0-milestone-9 to Tool Installation Metadata)
Affects Version/s: current
Description:
Gradle backend crawler does not see 1.0-milestone-9 release.
And
http://mirrors.jenkins-ci.org/updates/updates/hudson.plugins.gradle.GradleInstaller.json
does not list it anymore
https://github.com/jenkinsci/backend-crawler/blob/master/gradle.groovy#L12
must be updated to
{code}def baseUrl = 'http://services.gradle.org/distributions/'{code}
was:
Gradle 1.0-milestone-9 was released on 13/03/2012. I manually added it to the
hudson.plugins.gradle.GradleInstaller file, but Jenkins overwrote the file this
morning breaking my builds until I manually re-added the version and reloaded
the config.
Is there an easier way of maintaining this?
Component/s: gradle
infrastructure
> Update Gradle backend-crawler to new artifacts location
> --------------------------------------------------------
>
> Key: JENKINS-13093
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13093
> Project: Jenkins
> Issue Type: Improvement
> Components: core, gradle, infrastructure
> Affects Versions: current
> Reporter: stevendick
>
> Gradle backend crawler does not see 1.0-milestone-9 release.
> And
> http://mirrors.jenkins-ci.org/updates/updates/hudson.plugins.gradle.GradleInstaller.json
> does not list it anymore
> https://github.com/jenkinsci/backend-crawler/blob/master/gradle.groovy#L12
> must be updated to
> {code}def baseUrl = 'http://services.gradle.org/distributions/'{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
