[JENKINS-12568] Jenkins Gerrit Trigger plugin 2.3.1 doesnot report back build success/failure to Gerrit

When a user rolled back from a snapshot version the startup log seems filled with CNF Exceptions from the plugin not being loaded correctly.

Other things like the AdjunctManager is mentioned as well in the error log, so I am don't think it is the plugin's fault.

---------------------------------Old issue-----------------------------------------------------------

We are currently running Jenkins version 1.449 and Gerrit Trigger Plugin version 2.3.2.

The Gerrit Trigger plugin triggers Jenkins build jobs when a patch set is created in Gerrit code review. However, once the Jenkins build jobs complete, the plugin does not report the status back to Gerrit.

This has been happening quite often, like, once a week. Restarting the Gerrit Trigger does not fix the problem. So, we end up restarting Jenkins.

Any ideas on what is happening here and how we can resolve this issue and stop it from recurring?

---
Originally reported by nvsurya, imported from: Jenkins Gerrit Trigger plugin 2.3.1 doesnot report back build success/failure to Gerrit

• assignee: kohsuke
  
• status: Open
  
• priority: Major
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-06
  

Raw content of original issue

When a user rolled back from a snapshot version the startup log seems filled with CNF Exceptions from the plugin not being loaded correctly.

Other things like the AdjunctManager is mentioned as well in the error log, so I am don't think it is the plugin's fault.


---------------------------------Old issue-----------------------------------------------------------

We are currently running Jenkins version 1.449 and Gerrit Trigger Plugin version 2.3.2.

The Gerrit Trigger plugin triggers Jenkins build jobs when a patch set is created in Gerrit code review. However, once the Jenkins build jobs complete, the plugin does not report the status back to Gerrit.

This has been happening quite often, like, once a week. Restarting the Gerrit Trigger does not fix the problem. So, we end up restarting Jenkins.

Any ideas on what is happening here and how we can resolve this issue and stop it from recurring?

• environment: Jenkins master is running on Ubuntu and slave nodes are running on Windows 2008 R2

2 attachments

- [jenkins.err.log](https://issues.jenkins.io/secure/attachment/21467/jenkins.err.log)
- [jenkins.out.log](https://issues.jenkins.io/secure/attachment/21468/jenkins.out.log)

Start by reviewing the attached jenkins.err.log and jenkins.out.log for the failure around build completion and Gerrit status reporting. Reproduce the issue with Jenkins 1.449 and the Gerrit Trigger plugin, then verify that successful and failed builds report their status to Gerrit without restarting Jenkins.

Written by the indexing model from the issue text.