Well, if core will support "namespaces" for plugins (i.e. plugin's id is 'plugin-name' now, but it might be 'jenkinsci/plugin-name', 'bsideup/plugin-name', etc), permissions will be managed automatically by GitHub. Also, it will allow publishing forks of plugins.
In fact, it's already possible with Jucies - one can create descriptor named like 'bsideup.plugin-name' in '/plugins' folder of Jucies, so it will not overlap with 'plugin-name'. Of couse, it's not the way how plugins are being managed right now in Jenkins ecosystem, but it's more closer to some other CI/CD systems, i.e. Wercker, where steps identified by github's slug (i.e. 'bsideup/my-super-step') On Sat, Apr 30, 2016 at 12:44 PM Oleg Nenashev <[email protected]> wrote: > It becomes more and more interesting :) > I'm not sure how we can manage permissions for such kind of ecosystem, but > it definitely doable from the technical PoV. > > четверг, 28 апреля 2016 г., 12:44:59 UTC+2 пользователь 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/ab2c7834-9de6-48cf-bcba-8e820cfa5fd8%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/ab2c7834-9de6-48cf-bcba-8e820cfa5fd8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAAJdKX%3DWWxMPbGmbPtiGEsN91Oj3%2BxryOJELWcLGCjHMK1jhSA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
