jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-35379] gerrit-trigger no longer triggers build

Open
#786 6 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

After updating gerrit-trigger from 2.20.0 to 2.21.0 jobs no longer get triggered when a change gets pushed to Gerrit. Manually trying to trigger a Gerrit event manually doesn't work either. Sometimes it reports that a job was triggered (but that job never appears in the build queue), sometimes it claims that no job was triggered.

First I thought it might be caused by our Gerrit version, so I upgraded that from 2.10.5 to 2.12.2, but that didn't help.

It worked nicely before the upgrade of gerrit-trigger, and started to work again after I downgraded to 2.20.0.

---
Originally reported by ickersep, imported from: gerrit-trigger no longer triggers build


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

Raw content of original issue

After updating gerrit-trigger from 2.20.0 to 2.21.0 jobs no longer get triggered when a change gets pushed to Gerrit. Manually trying to trigger a Gerrit event manually doesn't work either. Sometimes it reports that a job was triggered (but that job never appears in the build queue), sometimes it claims that no job was triggered.

First I thought it might be caused by our Gerrit version, so I upgraded that from 2.10.5 to 2.12.2, but that didn't help.

It worked nicely before the upgrade of gerrit-trigger, and started to work again after I downgraded to 2.20.0.

  • environment: Jenkins 1.651.2, Gerrit 2.12.2, gerrit-trigger 2.21.0 (without REST API enabled)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.