Afaik admin role is granted in general now, since the introduction of danger zone permission protection.
I’m admin on a plugin that was hosted a couple of months ago, without me asking for it at all... Thanks Tim On Tue, 28 May 2019 at 18:58, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > We usually do not grant ADMIN role permissions to maintainers, but some > plugins indeed use admin. I prefer to focus on a more common case in the > guidelines > > BR, Oleg > > On Tue, May 28, 2019, 18:40 Tim Jacomb <timjaco...@gmail.com> wrote: > >> I’m pretty sure maintainers can just add the app themselves as it’s >> approved for the org, assuming they have admin permission on the repo >> >> I didn’t need an infra ticket when I set it up on the slack plugin... >> >> Thanks >> Tim >> >> On Tue, 28 May 2019 at 15:02, Oleg Nenashev <o.v.nenas...@gmail.com> >> wrote: >> >>> I agree it makes sense to document the steps. >>> >>> Basically it is... >>> >>> 1. Create ./github/release-drafter.yml file >>> - Extend the global config there >>> - Define your labeling and versioning scheme by overriding fields >>> - Examples: >>> - Role Strategy plugin: >>> >>> https://github.com/jenkinsci/role-strategy-plugin/blob/master/.github/release-drafter.yml >>> - ci.jenkins.io-runner: >>> https://github.com/jenkinsci/ci.jenkins.io-runner >>> 2. Create an INFRA ticket with component=github for enabling >>> Release Drafter in the repo. Assign to Oleg to improve the response time >>> >>> Order of steps does not really matter. I enabled Release drafter for >>> Platform Labeler and Plugin POM >>> >>> BR, Oleg >>> >>> >>> >>> On Tue, May 28, 2019 at 3:37 PM Mark Waite <mark.earl.wa...@gmail.com> >>> wrote: >>> >>>> I'd like to try it on the platformlabeler-plugin. >>>> >>>> On Sat, May 25, 2019 at 5:29 AM Oleg Nenashev <o.v.nenas...@gmail.com> >>>> wrote: >>>> >>>>> Since there is a consensus in this thread, I went ahead and >>>>> implemented this story: >>>>> >>>>> - Default configuration: >>>>> >>>>> https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml >>>>> - Pull request which merges the configuration for BlueOcean and >>>>> Configuration-as-Code plugins: >>>>> https://github.com/jenkinsci/.github/pull/1 >>>>> - Usage examples: >>>>> - Role Strategy plugin: >>>>> >>>>> https://github.com/jenkinsci/role-strategy-plugin/blob/master/.github/release-drafter.yml >>>>> - ci.jenkins.io-runner: >>>>> https://github.com/jenkinsci/ci.jenkins.io-runner >>>>> >>>>> Some notes about the current default config: >>>>> >>>>> - Default tag template (tag-template) does not make much sense, >>>>> because Maven Release plugin in Plugin POM uses the >>>>> ${artifactId}-${version} tag format by default. It needs to be >>>>> overridden >>>>> in repos (see the linked examples) >>>>> - Jenkins plugins use different versioning format. Release Drafter >>>>> defaults to semver <https://semver.org/>, but the majority of >>>>> Jenkins plugins uses the two-digit version number. That;s why I used >>>>> it as >>>>> a default in the global config >>>>> - it can be also overridden in repos, see ci.jenkins.io-runner >>>>> config >>>>> >>>>> <https://github.com/jenkinsci/ci.jenkins.io-runner/blob/master/.github/release-drafter.yml> >>>>> - Current replacer regexps target the common "[JENKINS-1234] - >>>>> Change description" templates only, but we can extend the, >>>>> >>>>> Obviously, contributions to the default template (and to other GitHub >>>>> app templates) are more than welcome. If you want to try out Release >>>>> Drafter in your repos, let me know. Disclaimer: see the permissions >>>>> concerns above. >>>>> >>>>> Best regards, >>>>> Oleg >>>>> >>>>> On Saturday, May 25, 2019 at 1:26:38 PM UTC+2, Daniel Beck wrote: >>>>>> >>>>>> >>>>>> >>>>>> > On 24. May 2019, at 19:23, James Nord <jn...@cloudbees.com> wrote: >>>>>> > >>>>>> > If there was a way to release community plugins from our infra then >>>>>> you could do this with a simple command without the need to grant any >>>>>> permissions to apps. >>>>>> >>>>>> I know of a proposal supposed to be landing soon related to that :) >>>>>> >>>>>> -- >>>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/6bab3eaa-e979-480e-b8c3-4b5425d600de%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/6bab3eaa-e979-480e-b8c3-4b5425d600de%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> -- >>>> Thanks! >>>> Mark Waite >>>> >>>> -- >>>> >>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-dev/dOs8YRQwQiI/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> jenkinsci-dev+unsubscr...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFQdkjd972M%3D8Zj3%3Ddf-upAXLV41vM_nGu7Dk1zjNHW6A%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFQdkjd972M%3D8Zj3%3Ddf-upAXLV41vM_nGu7Dk1zjNHW6A%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDnaquWT7RfmFukVWnyVmqHS_gCmDsbT28xBJjpgA0jxw%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDnaquWT7RfmFukVWnyVmqHS_gCmDsbT28xBJjpgA0jxw%40mail.gmail.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 a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/dOs8YRQwQiI/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> jenkinsci-dev+unsubscr...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif%2BMusRivM2ycG-XhxybW8v%2BggVah3v4gj8FrA9txazsw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif%2BMusRivM2ycG-XhxybW8v%2BggVah3v4gj8FrA9txazsw%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCkQkhWM5UaFmoY1pA8K%2B9d5UztBEDtr21_weQqOYusZA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCkQkhWM5UaFmoY1pA8K%2B9d5UztBEDtr21_weQqOYusZA%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic04k%3Dw2%2B%3DzqTV13Ozd%2BCa3QVwzs7aEMuSgBpnb1kWzKw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
