Thanks Luca, it's a big help. I found a nice thread (with you and Ben, of course) that covers this exact question.
For reference: https://groups.google.com/g/repo-discuss/c/Bp36i7B3Uqo/m/3fxKgceVAAAJ On Friday, December 3, 2021 at 1:26:16 PM UTC-8 lucamilanesio wrote: > Possibly a question for the repo-discuss mailing list? > > The Checks plugin isn't a mandatory requirement of the Gerrit Code Review > plugin: if you have it, it can be used. If you don’t have it, you’ll keep > on using the labels. > > HTH > > Luca. > > On 3 Dec 2021, at 15:49, 'Wade Carpenter' via Jenkins Developers < > [email protected]> wrote: > > It's about the gerrit-code-review-plugin jenkins plugin, > https://github.com/jenkinsci/gerrit-code-review-plugin#integrating-with-the-gerrit-checks-plugin. > > It's using the now-obsolete gerrit checks plugin to publish the build > status back to gerrit. The gerrit change is about restructing the way that > CI systems are integrated with gerrit, so this plugin is impacted. > > > On Thursday, December 2, 2021 at 8:24:36 PM UTC-8 [email protected] > wrote: > >> I'm sorry but what does this have to do with Jenkins? >> >> On Thu., Dec. 2, 2021, 8:14 p.m. 'Wade Carpenter' via Jenkins Developers, >> <[email protected]> wrote: >> >>> Hi folks, >>> >>> (I was torn betwen -dev and -users for this thread, so hopefully I got >>> it right!) >>> >>> While I was looking at https://gerrit.googlesource.com/plugins/checks >>> today, >>> I saw the following: >>> >>> *DEPRECATION NOTICE* >>> *The Gerrit team at Google has decided to discontinue work on the checks >>> plugin. The recommended solution is Checks UI >>> <https://gerrit-review.googlesource.com/Documentation/pg-plugin-checks-api.html> >>> which >>> surfaces results from an external CI/analysis system.* >>> >>> This seems to suggest that either we need to come up with a gerrit >>> "jenkinsci" plugin to provide a checks UI, or consider some other approach. >>> At this point I'm sorta waiting to see which direction >>> gerrit-review.googlesource.com goes in, but I was also wondering if >>> anyone here has thoughts on this. >>> >>> Thanks! >>> Wade >>> >>> >>> >>> -- >>> 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/0aae5971-4e08-4570-94d8-742ad4deddc7n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/0aae5971-4e08-4570-94d8-742ad4deddc7n%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 [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/239be687-fead-4631-b0a6-e3e3e511f4d3n%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/239be687-fead-4631-b0a6-e3e3e511f4d3n%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6bf78485-7d9a-4968-b73c-a7ad1d6daeb6n%40googlegroups.com.
