> On 06.09.2016, at 01:47, Slide <[email protected]> wrote: > > Ok, that works. How will plugin maintainers manage what is shown when a > plugin is selected?
The data is collected from the update center, which in turn uses a combination of POM and wiki (maintainer, plugin name, release date, …), the infra-statistics (installation counts), and plugin wiki page (documentation). The idea is that all of these sources are periodically updated -- not sure how well that's currently implemented though. We may implement something like Git repo based plugin docs in the future, but that would be opt-in. > Also, the "Download" option seems a little odd since most people would use > the plugin manager in a Jenkins install to do plugin installs, or is that > changing? Nothing's changing in Jenkins. I think we'll make the 'download' a popup explaining about the plugin manager in Jenkins, and still allow manual download for people with offline instances -- basically deemphasizing the "here's a file for you" part of the "Download" button. Also, in the thread on the dev list I suggested we could do something like a "Tweet this" button -- "Download in Jenkins" -- which would only require you to configure a Jenkins URL in HTML 5 local storage, or a cookie, to make it work from JS. This would require a change in Jenkins though. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/D4463375-B301-4BCD-A2DE-A103A8087B5A%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
