Using Jenkins 'Gerrit Checks API' plugin with Gerrit 'checks-jenkins' plugin

79 views
Skip to first unread message

Piotr Szlązak

unread,
Dec 8, 2025, 12:03:03 PM (8 days ago) Dec 8
to Repo and Gerrit Discussion
Hello!
Recently I was testing Gerrit Checks API plugin [1] on my Jenkins instance.
This was done to test checks-jenkins plugin [2] on my Gerrit instance.

Gerrit Checks API plugin [1] depends on Lucene Search plugin [3].
And here I faced following issues:
- by default Lucene Search plugin collects and indexes console logs
- console log index grows very fast - on my not-so-active Jenkins instance it was 14 GB after 3 days of work. In another attempt - it was 45 GB after 2 days of work
- both my tests ended with Lucene Search plugin crashing. There were some problems related to accessing the files. Maybe too many write attempts for console log?

I raised an Issue/Feature Request for Lucene Search plugin to make console logs indexing configurable [4].

Why am I writing about here? I noticed that Thomas Dräbing is maintainer of Lucene Search and Gerrit Checks API plugins. Also Luca is maintainer of Gerrit Checks API plugin.
Knowing that Checks API in Gerrit is a preferred way to collect statuses from CI [5], maybe you guys will be able to help with implementing this feature? Especially that Jenkins is still a quite popular CI.


Regards,
Piotr

Luca Milanesio

unread,
Dec 9, 2025, 9:31:59 AM (7 days ago) Dec 9
to Repo and Gerrit Discussion, Luca Milanesio

On 8 Dec 2025, at 17:03, Piotr Szlązak <piotr....@gmail.com> wrote:

Hello!
Recently I was testing Gerrit Checks API plugin [1] on my Jenkins instance.
This was done to test checks-jenkins plugin [2] on my Gerrit instance.

Gerrit Checks API plugin [1] depends on Lucene Search plugin [3].
And here I faced following issues:
- by default Lucene Search plugin collects and indexes console logs
- console log index grows very fast - on my not-so-active Jenkins instance it was 14 GB after 3 days of work. In another attempt - it was 45 GB after 2 days of work
- both my tests ended with Lucene Search plugin crashing. There were some problems related to accessing the files. Maybe too many write attempts for console log?

I raised an Issue/Feature Request for Lucene Search plugin to make console logs indexing configurable [4].

AFAIK they aren’t production-ready.

The one we use in Jenkins for building Gerrit Code Review *IS* production-ready and we use it daily.
See [6] and when I presented it [7].


Why am I writing about here? I noticed that Thomas Dräbing is maintainer of Lucene Search and Gerrit Checks API plugins. Also Luca is maintainer of Gerrit Checks API plugin.
Knowing that Checks API in Gerrit is a preferred way to collect statuses from CI [5], maybe you guys will be able to help with implementing this feature? Especially that Jenkins is still a quite popular CI.

I am pretty much fully booked at the moment, do you have time or budget to invest on it?

Luca.


Regards,
Piotr

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/5cdee29e-6ac8-48f9-a125-e846bc0c492dn%40googlegroups.com.

Piotr Szlazak

unread,
Dec 10, 2025, 5:04:42 PM (6 days ago) Dec 10
to Luca Milanesio, Repo and Gerrit Discussion
On Tue, Dec 9, 2025 at 3:32 PM Luca Milanesio <luca.mi...@gmail.com> wrote:


On 8 Dec 2025, at 17:03, Piotr Szlązak <piotr....@gmail.com> wrote:

Hello!
Recently I was testing Gerrit Checks API plugin [1] on my Jenkins instance.
This was done to test checks-jenkins plugin [2] on my Gerrit instance.

Gerrit Checks API plugin [1] depends on Lucene Search plugin [3].
And here I faced following issues:
- by default Lucene Search plugin collects and indexes console logs
- console log index grows very fast - on my not-so-active Jenkins instance it was 14 GB after 3 days of work. In another attempt - it was 45 GB after 2 days of work
- both my tests ended with Lucene Search plugin crashing. There were some problems related to accessing the files. Maybe too many write attempts for console log?

I raised an Issue/Feature Request for Lucene Search plugin to make console logs indexing configurable [4].

AFAIK they aren’t production-ready.

I guess my findings make them even less production-ready. Lucene Search is especially unstable, imho.
 
The one we use in Jenkins for building Gerrit Code Review *IS* production-ready and we use it daily.
See [6] and when I presented it [7].

I watched your presentation with great interest.
Also I checked what kind of requests I can see if I go to gerrit-review.googlesource.com and check the 'Checks' tab for a random change [8].
By comparing responses [9] and [10] with a definition of a response structure for checks plugin [11] I would say, checks plugin [12] is still used there. AFAIK this plugin is marked as deprecated. Gerrit Checks API / UI should be used instead.
Also Gerrit Code Review plugin mentions it integrates with checks plugin [13].

Due to the above, I was testing setup based on Gerrit Checks API / UI.
 


Why am I writing about here? I noticed that Thomas Dräbing is maintainer of Lucene Search and Gerrit Checks API plugins. Also Luca is maintainer of Gerrit Checks API plugin.
Knowing that Checks API in Gerrit is a preferred way to collect statuses from CI [5], maybe you guys will be able to help with implementing this feature? Especially that Jenkins is still a quite popular CI.

I am pretty much fully booked at the moment, do you have time or budget to invest on it?

Unfortunately, the only thing I can offer at the moment are results / conclusions from my tests.
Sorry if I sounded like I'm pushing you to do something about it. I wanted to bring your attention to a potential loophole in Gerrit Checks API / UI adoption among Jenkins users.
I hope you find my findings useful for building a more complete Gerrit ecosystem.

Regards!
--
Piotr

Sven Selberg

unread,
Dec 11, 2025, 2:38:50 AM (5 days ago) Dec 11
to Repo and Gerrit Discussion
On Wednesday, December 10, 2025 at 11:04:42 PM UTC+1 Piotr Szlazak wrote:
On Tue, Dec 9, 2025 at 3:32 PM Luca Milanesio <luca.mi...@gmail.com> wrote:


On 8 Dec 2025, at 17:03, Piotr Szlązak <piotr....@gmail.com> wrote:

Hello!
Recently I was testing Gerrit Checks API plugin [1] on my Jenkins instance.
This was done to test checks-jenkins plugin [2] on my Gerrit instance.

Gerrit Checks API plugin [1] depends on Lucene Search plugin [3].
And here I faced following issues:
- by default Lucene Search plugin collects and indexes console logs
- console log index grows very fast - on my not-so-active Jenkins instance it was 14 GB after 3 days of work. In another attempt - it was 45 GB after 2 days of work
- both my tests ended with Lucene Search plugin crashing. There were some problems related to accessing the files. Maybe too many write attempts for console log?

This was more or less our analysis of using Lucene Search plugin and why we opted to not use this setup.
We haven't had time to look into other options, but one hot candidate is to use an Eiffel events driven solution.
Reply all
Reply to author
Forward
0 new messages