jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-21573] Make possible to manually trigger builds based on different than 'patchset-created' event type

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

Description

We for example want to use Gerrit trigger also for triggering regular (not staging) builds when change is merged. It is possible, but if something goes wrong it is not possible to trigger such build manually.

---
Originally reported by bosy, imported from: Make possible to manually trigger builds based on different than 'patchset-created' event type


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

Raw content of original issue

We for example want to use Gerrit trigger also for triggering regular (not staging) builds when change is merged. It is possible, but if something goes wrong it is not possible to trigger such build manually.

Contributor guide

Open the contributing guide

Research direction

The issue concerns manual triggering in the gerrit-trigger-plugin for event types other than patchset-created, including builds after a change is merged. Start by tracing the plugin's manual trigger and event-type handling; the payload names no files or tests. Done means the requested non-patchset build can be triggered manually and the behavior is covered by appropriate verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.