[JENKINS-34639] Jenkins job doesn't start when gerrit event occurs

Jenkins version : 1.647

Gerrit Trigger : 2.18.3

AWS Server configuration

16 Cores, 30GB RAM.

We have setup gerrit and jenkins in AWS systems for Android ecosystem.

When a +1 is given in gerrit, we want jenkins to start the android build.

The jenkins jobs works well sometimes, but misses the event many times.

Only if we restart the jenkins , the job starts working well.

But after sometime same problem happens.

We have internal memory of 99GB where jenkins is installed and jobs-> workspace is in /mnt folder of AWS. There is no problem in output of the job.

Problem is that job is not starting for gerrit event.

Is this problem related to internal memory by any chance? Please suggest where can i get the logs for issue and can post the same.

---
Originally reported by anushreeag, imported from: Jenkins job doesn't start when gerrit event occurs

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

Raw content of original issue

Jenkins version : 1.647

Gerrit Trigger : 2.18.3


AWS Server configuration

16 Cores, 30GB RAM.


We have setup gerrit and jenkins in AWS systems for Android ecosystem.

When a +1 is given in gerrit, we want jenkins to start the android build.

The jenkins jobs works well sometimes, but misses the event many times.

Only if we restart the jenkins , the job starts working well.

But after sometime same problem happens.

We have internal memory of 99GB where jenkins is installed and jobs-> workspace is in /mnt folder of AWS. There is no problem in output of the job. 

Problem is that job is not starting for gerrit event.


Is this problem related to internal memory by any chance? Please suggest where can i get the logs for issue and can post the same.

environment

```
Jenkins version : 1.647

Gerrit Trigger : 2.18.3
```

No source files, tests, or entry points are named. Start by reviewing the gerrit-trigger-plugin event handling and the available Jenkins and Gerrit Trigger logs, then reproduce the missed +1 event after the system has been running for a while; done means the cause is identified and the job reliably starts from the event.

Written by the indexing model from the issue text.