I'd like to try it on the platformlabeler-plugin.

On Sat, May 25, 2019 at 5:29 AM Oleg Nenashev <[email protected]>
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 <[email protected]> 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 [email protected].
> 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 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/CAO49JtFQdkjd972M%3D8Zj3%3Ddf-upAXLV41vM_nGu7Dk1zjNHW6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to