Very nice! I love automation. :) On Thu, Aug 6, 2020 at 2:26 AM 'Olblak' via Jenkins Developers < [email protected]> wrote:
> Well done \o/ > > On Thu, Aug 6, 2020, at 8:54 AM, Tim Jacomb wrote: > > Hi all > > I’m happy to announce that the `buildPlugin()` library step that is used > by almost all plugins on ci.jenkins.io now uses the Warnings NG plugin > <https://plugins.jenkins.io/warnings-ng/> for static code analysis > reporting and quality control. > > We have set default quality gate for: > > - > > No new spotbugs issues > - > > No checkstyle issues > > Note: in order for spotbugs to calculate your initial issues you will need > your master branch ran once to establish a baseline > > You can customise the quality gates, however you wish (enable / disable > them, or adjust the severity of the warnings), see the documentation for > the pipeline-library > <https://github.com/jenkins-infra/pipeline-library/#optional-arguments> > and the Warnings NG <https://plugins.jenkins.io/warnings-ng/> > documentation. > > On top of the Warnings NG addition we have switched ci.jenkins.io over to > GitHub app authentication (mailing list post > <https://groups.google.com/g/jenkins-infra/c/VYXkHYS10oo/m/DUP7kVZOAQAJ>). > This gives us much higher rate limits and access to the GitHub checks API. > > Lastly we have installed the GitHub checks > <https://plugins.jenkins.io/github-checks/> plugin which is a GSoC 2020 > project by Kezhi Xiong which exposes an API allowing consuming plugins to > publish checks results and annotations to GitHub. > > > > > See Kezhi’s GSoC phase 2 demo on YouTube > <https://youtu.be/b67I6spBdTg?t=1517>. > > Next steps: > > - > > We hope to soon land support for the Code Coverage API plugin in > `buildPlugin()` - Code Coverage API plugin already has support for the > GitHub checks plugin. - Pull request > <https://github.com/jenkins-infra/pipeline-library/pull/153>. > - > > Kezhi and I will be hosting a Jenkins online meetup Mid August on > GitHub app authentication and the GitHub checks integration. > - > > Possibly some tuning of severity on some issues - see discussion > > <https://github.com/jenkins-infra/pipeline-library/pull/121#discussion_r465956892> > > > Feedback > > We would love any feedback, please feel free to provide it either here, in > Gitter <https://gitter.im/jenkinsci/github-checks-api> or in the issue > tracker for the respective component. > > Thanks > > Tim > > > -- > 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/CAH-3Bidxq1BJi8LYzj-ftWfzSkevYro4Z%2B38Bnpx-jqpsDNAsw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bidxq1BJi8LYzj-ftWfzSkevYro4Z%2B38Bnpx-jqpsDNAsw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > -- > 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/e8f770f1-a504-4139-bc51-5bb286739ca4%40www.fastmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/e8f770f1-a504-4139-bc51-5bb286739ca4%40www.fastmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAEot4ox04EBcB7P_k9FC4y76EL7iAJn9KvtK-36Sm9hocMVrCA%40mail.gmail.com.
