[Jenkins-infra] Proposal - Introducing Global Probot configuration for Release Drafter and other tools

[Oleg Nenashev]

Hi all,

Just another GitHub infrastructure thread is here. There is a number of
components which started using Release Drafter
<https://github.com/toolmantim/release-drafter> to automate management of
releases notes. Basically, this tool generates changelog drafts using pull
request metadata (commit headers, links, etc.). It is one of examples of
many Probot-based GitHub applications <https://probot.github.io/apps/>
which could help plugin maintainers and improve the contributor experience
within the organization.

Release Drafter usage examples:

   - Configuration As Code Plugin
   <https://github.com/jenkinsci/configuration-as-code-plugin/releases>
   - BlueOcean Plugin
   <https://github.com/jenkinsci/blueocean-plugin/releases>
   - Slack Plugin <https://github.com/jenkinsci/slack-plugin/releases>
   - BitBucket Branch Source Plugin
   <https://github.com/jenkinsci/bitbucket-branch-source-plugin/releases>
   - Jenkinsfile Runner
   <https://github.com/jenkinsci/jenkinsfile-runner/blob/master/CHANGELOG.md#10-beta-8---2019-05-18>

All components use pretty similar configuration files and labeling
strategies. For example, here is a Jenkinsfile Runner configuration file
<https://github.com/jenkinsci/jenkinsfile-runner/blob/master/.github/release-drafter.yml>.
You may see that this file defines labels, replacement logic for Jenkins
JIRA and CVE references, etc. Copy-paste across repositories is
problematic.Good news is that we could define configs on the org-wide basis.

Release Drafter is based on the Probot framework <https://probot.github.io/>
for GitHub apps. Probot allows managing application configs on the
org-level by introducing a new system config repository (documentation
<https://github.com/probot/probot-config/blob/master/README.md>).
Configurations can be then overridden by repositories if needed.

What do I propose?

   1. Create a Probot global configuration repository
   2. Add a sample Release Drafter configuration there. It will be reviewed
   together with all current users so that we come up with a convenient
   Release Drafter configuration
   3. Open discussion for other GitHub applications being used in
   jenkinsci. We could have global configs there as well

Would appreciate any feedback. If there is a consensus about having such
global configuration repo, I am happy to implement it.

BR, Oleg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20190523/5ec3561a/attachment.html>