+1 would be great, I've done some ground laying work for it here: https://github.com/jenkinsci/github-branch-source-plugin/pull/269
It requires a github-api-plugin version to be published with a recent ish version of github-api Thanks Tim On Mon, 27 Jan 2020 at 16:09, Raihaan Shouhell <raihaanhims...@gmail.com> wrote: > I think having a checks api would be great. > Reports sending checks back to the change request would be a useful > feature. > > > On Monday, 27 January 2020 20:57:31 UTC+8, Oleg Nenashev wrote: >> >> Just to bump this thread, we consider adding Checks API integration as a >> GSoC 2020 project idea. >> We had a preliminary discussion with Ulli Hafner (Warnings NG) and other >> parties. >> >> If someone is interested to join the project, please let me know >> >> On Thursday, May 10, 2018 at 5:56:28 PM UTC+2, Jesse Glick wrote: >>> >>> On Thu, May 10, 2018 at 5:37 AM, Steven F <steven...@gmail.com> wrote: >>> > The examples in the article show elements such as linting, >>> > build, static analysis as separate and individually runnable things. >>> In >>> > Jenkins 2.x Pipeline it feels like bundling these things together is >>> more >>> > encouraged. >>> >>> Well, it is generally more straightforward to have those things be run >>> as part of a single Jenkins build, triggered by SCM changes. What is >>> missing is an API which would allow Jenkins report plugins (`Publisher >>> & SimpleBuildStep`, for example) to indicate to the system that there >>> is some information to be displayed in an abstract “change request”, >>> perhaps associated with source code lines, which would then be >>> implemented by `github-branch-source` with the Checks API. >>> >>> jxpe...@godaddy.com wrote: >>> > just rerunning the job from github would save a step >>> >>> See JENKINS-45455 for rerunning generally; again we would need a new >>> API to allow this is to be integrated with in-PR “chatops” triggers, >>> so that `github-branch-source` could receive GH events and refire them >>> as requests to rerun parts of a build, which >>> `pipeline-model-definition` would then interpret as a Declarative >>> build trigger. >>> >>> All this would allow you to do more from GitHub and less from Blue >>> Ocean or the Jenkins “classic” UI. @abayer has done the most work in >>> this area and should probably be commenting. >>> >> -- > 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/fa0449e3-53ec-42d2-a788-cad59557d4d2%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/fa0449e3-53ec-42d2-a788-cad59557d4d2%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicOTe9yuTQsBoPdY-ra2FjQzONHqBvkGyeJNRiKd%2BsnkQ%40mail.gmail.com.
