jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-30716] Gerrit plugin quiet period

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

Description

Add posibility to turn on the quiet period to group changes in batches: if a new change is merge within quiet period - reset the quiet period instead of adding another build to the queue.

Would that be possible? The situation in which I currently am is that I'm using gerrit plugin to trigger builds for gerrit's awesome replication event feature which lets me to wait for the change to be replicated to mirror repository. The problem is that when multiple changes come in a batch - all of them are reflected as instances of a build.

Now with SCM trigger it is possible to overcome this by adding a quiet period, but with gerrit trigger this doesn't work.

---
Originally reported by naj_oknetul, imported from: Gerrit plugin quiet period


  • assignee: rsandell
  • status: Open
  • priority: Minor
  • component(s): gerrit-trigger-plugin
  • label(s): configuration, pipeline
  • resolution: Unresolved
  • votes: 1
  • watchers: 1
  • imported: 2025-12-06

Raw content of original issue

Add posibility to turn on the quiet period to group changes in batches: if a new change is merge within quiet period - reset the quiet period instead of adding another build to the queue.

Would that be possible? The situation in which I currently am is that I'm using gerrit plugin to trigger builds for gerrit's awesome replication event feature which lets me to wait for the change to be replicated to mirror repository. The problem is that when multiple changes come in a batch - all of them are reflected as instances of a build.

Now with SCM trigger it is possible to overcome this by adding a quiet period, but with gerrit trigger this doesn't work.

  • environment: Jenkins 1580.3, gerrit trigger plugin 2.14.0

Contributor guide

Open the contributing guide

Research direction

No source file, test, or entry point is named. Start by locating the Gerrit trigger's build-queue scheduling path and comparing it with the SCM trigger quiet-period behavior described in the issue. Done means successive changes within the configured period are grouped into one build rather than queued separately.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.