jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-32323] Trigger a Gerrit event manually generate Event CreatedOn is null

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

Description

Dear all

When i want to manually select a patch set and trigger it, then get message in logger:

Event CreatedOn is null...Gerrit Server might not support attribute eventCreatedOn. Will NOT persist this event and Missed Events will be disabled!

but task is select and it start to building project.

The gerrit trigger plugin can automatically received events and start task to build without error.

---
Originally reported by sina_tad, imported from: Trigger a Gerrit event manually generate Event CreatedOn is null


  • assignee: sina_tad
  • status: Open
  • priority: Minor
  • component(s): gerrit-trigger-plugin
  • label(s): gerrit-trigger, git, jenkins, plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-06

Raw content of original issue

Dear all
When i want to manually select a patch set and trigger it, then get message in logger:

Event CreatedOn is null...Gerrit Server might not support attribute eventCreatedOn. Will NOT persist this event and Missed Events will be disabled!

but task is select and it start to building project.

The gerrit trigger plugin can automatically received events and start task to build without error.

environment

```
Jenkins version: 1.625

gerrit-trigger-plugin: 2.18.3

gerrit version: 2.11.3
```

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Reproduce the manual patch-set trigger with Jenkins 1.625, gerrit-trigger-plugin 2.18.3, and Gerrit 2.11.3, then trace the code producing the “Event CreatedOn is null” warning. Done means the manual trigger behaves correctly without the reported warning while automatic Gerrit events continue to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, java
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.