[
https://issues.jenkins-ci.org/browse/JENKINS-12568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Surya NV updated JENKINS-12568:
-------------------------------
Summary: Jenkins Gerrit Trigger plugin 2.3.1 doesnot report back build
success/failure to Gerrit (was: Rolling back Gerrit Trigger from snapshot
version causes it not to be able to loadc)
I was able to make some progress and rollback from the snapshot version of
Gerrit Trigger back to the 2.3.1 version. Gerrit Trigger plugin version 2.3.1
still does not report back the build success/failure back to Gerrit although I
recall reading that this known issue has been resolved in the 2.3.1 version in
some Jenkins forums.
The plugin kicks off a build when a patch set is submitted and reports back to
Gerrit that the build has started. However, when the build completes it does
not want to report back to Gerrit about the success/failure. Our production
environment is impacted for the past week now. Any pointers/help to resolve
this issue will be timely and greatly appreciable.
> Jenkins Gerrit Trigger plugin 2.3.1 doesnot report back build success/failure
> to Gerrit
> ---------------------------------------------------------------------------------------
>
> Key: JENKINS-12568
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12568
> Project: Jenkins
> Issue Type: Bug
> Components: core, gerrit-trigger
> Affects Versions: current
> Environment: Jenkins master is running on Ubuntu and slave nodes are
> running on Windows 2008 R2
> Reporter: Surya NV
> Assignee: Kohsuke Kawaguchi
> Attachments: jenkins.err.log, jenkins.out.log
>
>
> 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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
