Hi Tomas, I checked your links regarding the plugins. I created a micro site based on http://updates.jenkins-ci.org/current/update-center.json you can find the source in https://github.com/scherler/jenkins-plugin-site and a demo in http://plugin-site.stax.net/ (it is still under development).
It is a simple rendering of the plugin list as taken from updates.jenkins-ci.org/current/update-center.json to make the information of plugins searchable and filterable. It is based on a node server that processes the jsonp creates a in.memory "poor-mans" database (if you want to go so far to call it db) and then serves as REST backend e.g. http://plugin-site.stax.net/plugins or http://plugin-site.stax.net/labels. The front end is based on react.js and redux. That would be easy adoptable to pull from different market places. I actually think even having the current plugins in a market place would allow as well features like rating, favorites, custom grouping, etc. Instead of using above jsonp source I would rather use a REST/CORS server that provides thus data. salu2 On Monday, May 2, 2016 at 3:08:42 PM UTC+2, Tomas Bjerre wrote: > > This is great! > > I tried to come up with a solution for this myself. The plugins are (in my > opinion) the only good thing about Jenkins. I would never use it if it was > not for the plugins. A solution like this is needed, so that plugin > developers can avoid situations like this: > > > https://groups.google.com/forum/#!searchin/jenkinsci-dev/git-changelog/jenkinsci-dev/Jsck8GgWwJg/GAZV8Y0-CAAJ > > Competition is a good thing. But competition is not allowed among Jenkins > plugins. Its very frustrating when you dont want to contribute to an > existing plugin. Perhaps because of the way a problem is solved in an > existing one. If you want to solve the same problem, or similar, in a > different way, you will be denied. Or forced to merge you code into the > existing one. Like in my case with the git-changelog-plugin. It is now > causing confusion among users. > > I'd like to see an independent marketplace where plugins can be published, > rated and reviewed. Just like the Atlassian Marketplace works. I started > working on something like that ( > https://github.com/tomasbjerre/jenkins-plugins/ and > http://www.jenkins-plugins.com/) but have not had time to finish it. > > -Tomas > > Den torsdag 28 april 2016 kl. 12:44:59 UTC+2 skrev Sergei Egorov: >> >> Hey everyone, >> >> Remember Jucies? ( https://github.com/jucies/releases ) - experimental >> update center for Jenkins with releases directly from GitHub? >> >> Today it became much better! >> >> Starting from today, GitHub releases will be used to release your plugin. >> That said, no publish, no PRs to update your plugin's version. Just create >> a release on GitHub and it will be hooked up by Jucies in a few minutes. >> >> For example, here is Pipeline View plugin released on Jucies: >> >> https://github.com/jucies/releases/blob/master/plugins/pipeline-view.properties >> >> As you can see - no version here, only repository reference, where >> release exists: >> https://github.com/jenkinsci/pipeline-view-plugin/releases >> >> >> >> Also, I'm happy to say that Build Graph Plugin and Build Name Setter >> Plugin were using Jucies to release their plugins as well. Wooo! >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/bd46e706-e131-4956-b42c-7e56db1234ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
