Checks-jenkins plugin feedback

[Nuno Costa]

Hi All,

We are planning to include checks-jenkins plugin on our setup and I would like to ask for the community feedback on it usage.

From the tests I've done, it's setup seems to be more involved from the end user(CI Admins) than from the Gerrit Admin side.

In terms of Gerrit performance, I also don't expect any additional load since the build status checks are between the browser and Jenkins. Gerrit is just serving the javascript file for the browser to run.

I found 2 possible bugs(signin and rerun buttons not working) when running against Gerrit 3.9.11 Java 11(I know it is EOL but baby steps :) ) that I will report as soon I run the same setup on Gerrit 3.10 and above to confirm if they are also affected.

Any feedback about the plugin usage is much appreciated.

Thanks,

Nuno

[Nasser Grainawi]

You probably want to build the tip of the master branch and try using that with 3.9: https://gerrit.googlesource.com/plugins/checks-jenkins/+log/refs/heads/master

I think it will just work, but there's a chance there's something version-specific in there.

 

Any feedback about the plugin usage is much appreciated.

Thanks,

Nuno

--
--
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/bded65a5-391d-4b57-9b9e-1b045f1460b7n%40googlegroups.com.

[Nuno Costa]

On Thursday, 2 October 2025 at 17:12:24 UTC+1 Nasser Grainawi wrote:

On Thu, Oct 2, 2025 at 3:28 AM Nuno Costa wrote:

Hi All,

We are planning to include checks-jenkins plugin on our setup and I would like to ask for the community feedback on it usage.

From the tests I've done, it's setup seems to be more involved from the end user(CI Admins) than from the Gerrit Admin side.

In terms of Gerrit performance, I also don't expect any additional load since the build status checks are between the browser and Jenkins. Gerrit is just serving the javascript file for the browser to run.

I found 2 possible bugs(signin and rerun buttons not working) when running against Gerrit 3.9.11 Java 11(I know it is EOL but baby steps :) ) that I will report as soon I run the same setup on Gerrit 3.10 and above to confirm if they are also affected.

You probably want to build the tip of the master branch and try using that with 3.9: https://gerrit.googlesource.com/plugins/checks-jenkins/+log/refs/heads/master

I think it will just work, but there's a chance there's something version-specific in there.

I've been testing with both our own build against check-jenkins master branch on gerrit 3.9.11 and using the master jar from https://gerrit-ci.gerritforge.com/plugin-manager/.

I also tested with official containers with same rerun and signin buttons issues.

• gerrit:3.10.8
• gerrit:3.11.5
• gerrit:3.12.2

Instead of a signin button, this is shown in the UI, with a 403:

Error while fetching results for checks-jenkins:
Error message from plugin 'checks-jenkins': {}

During my initial tests with no nginx configured and using the CORS jenkins plugin, I was able to see the button if I had setup the checks-jenkins incorrectly but if I set it correctly, the same 403 error would be shown.

Since I setup nginx, I cant reproduce that behaviour but the 403 error is the same. 

Regarding the rerun button, it shows(browser dev tools) this access returning a 404 using GET:

https://my.jenkins/job/3.10/2/gerrit-trigger-retrigger-this/
If I retrigger(Gerrit trigger jenkins plugin) the build in Jenkins, the build is retriggered, and I can see the same URL being used but it uses POST.

TIP: we are using a fork of Gerrit Trigger jenkins plugin based on 2.36.0 and curiously, the rerun button works.

My setup has been using Jenkins 2.528(+ gerrit-trigger Jenkins plugin 2.42.0 and gerrit-checks-api jenkins plugin 66.v3ef8b_f08f1f3), behind nginx, using self signed certificates.

I have these headers in nginx vhost, where cors_allowed_origin is a map that contains all the gerrit servers I want to allow access:

add_header 'Access-Control-Allow-Origin' $cors_allowed_origin always;

add_header 'Access-Control-Allow-Credentials' 'true' always;
add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS' always;
add_header 'Access-Control-Allow-Headers' 'Authorization,Content-Type,X-Requested-With' always;

Setting the Jenkins instance to properly make checks-jenkins work took a bit of time so it is possible I'm missing something.

Tomorrow, I will try open issues for these.

If anyone has some tips to fix these issues or general feedback regarding the plugin usage, I would appreciate.

Thanks,

Nuno

[Yash Chaturvedi]

Hi,

Don't know if you had lucene-search plugin installed in your setup (without nginx) but you'd need the lucene-search plugin installed along with CORS plugin to make the checks plugin on jenkins work correctly as mentioned in the docs [1]. 

[1] https://plugins.jenkins.io/gerrit-checks-api/#plugin-content-getting-started

Regards,

Yash

[Michael Nazzareno Trimarchi]

Hi

I give you an help

RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Port "443"

<IfModule mod_headers.c>
Header add Access-Control-Allow-Origin
"https://gerrit-review.amarulasolutions.com"
Header set Access-Control-Allow-Methods "*"
Header set Access-Control-Allow-Credentials true
</IfModule>

<Location />
ProxyPass http://127.0.0.1:8080/ nocanon
ProxyPassReverse http://127.0.0.1:8080/
</Location>

Michael

> --
> --
> 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/bd66768b-79bd-4724-ad93-ec3da3fa0b5en%40googlegroups.com.



--
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
mic...@amarulasolutions.com
__________________________________

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
in...@amarulasolutions.com
www.amarulasolutions.com