Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: sonar-gerrit-plugin
-
Labels:None
-
Environment:Jenkins 1.609.2 LTS
sonar-gerrit 1.0.6
gerrit trigger 2.18.3
-
Similar Issues:
Description
I recently installed sonar-gerrit plugin on Jenkins 1.609.2 LTS - due to plug-in dependency gerrit-trigger plugin upgraded from 2.16.0 to 2.18.3 version. After successful Jenkins restart, "Jenkins to Gerrit" connection breaks (No Git/Gerrit actions can be performed from Jenkins). However, from sonar-gerrit plug-in homepage, sonar-gerrit plug-in will work from Jenkins 1.580.1 onwards.
Could you please investigate why gerrit connection breaks when we install sonar-gerrit 1.0.6 & gerrit trigger 2.18.3 on Jenkins 1.609.2 LTS?
Do let me know if any other information is required.
Attachments
Issue Links
- relates to
-
JENKINS-33892 Add details of exception into logging
-
- Resolved
-
Activity
Hello. I have the same issue but I have no proxy setting up. My full description is explained on http://stackoverflow.com/q/40157708/2394026
How can I investigate myself and where can I see error logs of the plugin ? Jenkins is installed on Windows server.
Jenkins version 2.19.1 - Gerrit 2.13.2 - Plugin SonarGerrit 1.0.6 - Plugin Gerrit Trigger 2.21.1
Florent D.
Does it work with section "post score?" unchecked?
What category do you use for score posting? (Have you created it in Gerrit?)
Thanks for your fast answer.
It doesn't work without posting score. I still have the message "Unable to post review: Request failed." in analysis logs. Nothing changed on Gerrit UI and there is no messages in httpd_log log file (Gerrit server side).
I use the default "Code-Review" for posting score. It is already created in Gerrit.
Is there a way to add traces in a file to get more information about what doesn't work ?
Florent,
Extra logging will be available in the 1.0.7 release (see JENKINS-33892). It should be published shortly.
We put proxy to java params that runs a tomcat catalina by adding -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=yyyy in catalina.sh script.
I modified source code of this plugin adding some extra logging and we see in tomcat logs that this kind of request goes to this proxy that we used for updating Jenkins plugins. Other comunication in Jenkins was OK and we don't have any other problems.
Removing this settings and clean settings from jenkins plugin update page - resolve our problem but Jenkins is not able to perform automatic updates now.
Maybe you have similar config on nginx?
Regards