jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-27741] Jenkins fails to report gerrit notifications spontaneously and on restart.

Open
#712 11 comments 0 reactions 0 assignees View on GitHub
component:gerrit-trigger-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
226
Forks
289
PR merge metrics
No merged PRs in 30d

Description

A jenkins server which was communicating properly with gerrit, suddenly stops reporting both "Build Started" and build success or failure back to gerrit.

In an attempt to resolve, jenkins is restarted. Upon restart, the problem persists and this error message is seen in the jenkins log -

Apr 03, 2015 10:27:34 AM com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.actions.manual.ManualTriggerAction getServerConfig

SEVERE: Could not find server null

While the jenkins server is in this state, the gerrit server status shows as green under https://myjenkins/gerrit-trigger/ and the test connection button under https://myjenkins/gerrit-trigger/server/defaultServer/ reports success.

Also during this failure, the retrigger links vanish from gerrit verifier builds. Screenshot attached.

The problem went away after a second jenkins restart. After this restart, new gerrit builds show the retrigger links, but one which were run during the period of failure still don't show them.

---
Originally reported by csanders, imported from: Jenkins fails to report gerrit notifications spontaneously and on restart.


  • assignee: rsandell
  • status: Open
  • priority: Major
  • component(s): gerrit-trigger-plugin
  • resolution: Unresolved
  • votes: 5
  • watchers: 8
  • imported: 2025-12-06

Raw content of original issue

A jenkins server which was communicating properly with gerrit, suddenly stops reporting both "Build Started" and build success or failure back to gerrit.

In an attempt to resolve, jenkins is restarted. Upon restart, the problem persists and this error message is seen in the jenkins log -

Apr 03, 2015 10:27:34 AM com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.actions.manual.ManualTriggerAction getServerConfig
SEVERE: Could not find server null

While the jenkins server is in this state, the gerrit server status shows as green under https://myjenkins/gerrit-trigger/ and the test connection button under https://myjenkins/gerrit-trigger/server/defaultServer/ reports success.

Also during this failure, the retrigger links vanish from gerrit verifier builds. Screenshot attached.

The problem went away after a second jenkins restart. After this restart, new gerrit builds show the retrigger links, but one which were run during the period of failure still don't show them.

environment

```
Jenkins 1.596.1 (LTS)

Gerrit 2.10.1

Gerrit Trigger Plugin 2.12.0

All running on Ubuntu 12.0
```

2 attachments

- [gerrit-trigger-bug.txt](https://issues.jenkins.io/secure/attachment/29892/gerrit-trigger-bug.txt)
- [missing_retrigger.png](https://issues.jenkins.io/secure/attachment/29104/missing_retrigger.png)
> ![missing_retrigger.png](https://issues.jenkins.io/secure/attachment/29104/missing_retrigger.png)

Contributor guide

Open the contributing guide

Research direction

Start with com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.actions.manual.ManualTriggerAction#getServerConfig and the reported "Could not find server null" log entry. Reproduce the failure around restart and inspect how the configured defaultServer is resolved; done means build notifications and retrigger links continue working after restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.