GitHub's terribly coarse security API to the forefront once again! On Thu, May 23, 2019 at 6:09 AM Robert Sandell <[email protected]> wrote:
> +1 I've been hoping we do something like this for a while now but haven't > come up with anything myself :) > > Though it states on the Release Draft App page > <https://github.com/apps/release-drafter>: "Release Drafter requires full > write, because GitHub does not offer a limited scope for only writing > releases. *Don't install Release Drafter to your entire GitHub account* — > only add the repositories you want to draft releases on." > > /B > > Den tors 23 maj 2019 kl 10:38 skrev Oleg Nenashev <[email protected] > >: > >> 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 >> >> >> >> >> >> >> >> >> >> -- >> 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/CAPfivLDA%3DmXpKMz%3Dmo6qTYaAcrj56d0xJjQzOV2MtewdeCpgWA%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDA%3DmXpKMz%3Dmo6qTYaAcrj56d0xJjQzOV2MtewdeCpgWA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > *Robert Sandell* > Software Engineer > CloudBees, Inc. > [image: CloudBees-Logo.png] <http://www.cloudbees.com/> > E: [email protected] > Twitter: robert_sandell > > -- > 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/CALzHZS2%3DaU8EOdjbpDVRsnfx2CWCsdNyKoyQR1WmbtNLJpD5Vw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS2%3DaU8EOdjbpDVRsnfx2CWCsdNyKoyQR1WmbtNLJpD5Vw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker Senior Software Engineer, CloudBees -- 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/CAEot4oxfTeygvfFsF9eEbpo-VR8M3b-JFHDefF8eEg1y-L6ReQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
