jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-31774] Allow sending feedback on job queued

Open
#756 0 comments 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

Right now when a job is successfully triggered by an event, you will have no feedback until the job starts running, and when jenkins is loaded, that might take some time and confuses users that are not certain if their patch will or will not be checked by jenkins

---
Originally reported by dcaroest, imported from: Allow sending feedback on job queued


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

Raw content of original issue

Right now when a job is successfully triggered by an event, you will have no feedback until the job starts running, and when jenkins is loaded, that might take some time and confuses users that are not certain if their patch will or will not be checked by jenkins

Contributor guide

Open the contributing guide

Research direction

Review the gerrit-trigger-plugin component and the original JENKINS-31774 report to understand the requested queued-job feedback. Trace the existing event-triggered job flow before defining the user-visible behavior; the work is done when users receive clear feedback that their job was queued.

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.