jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-11431] job shouldn't completely hide "retrigger" link when new build is pending

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

Description

We have a setup where Gerrit triggers a job in Jenkins. When the build fails, normally there is a "retrigger" link on the left of the page to retrigger the build to happen again.

== What I did:

Navigated to the build page for this job because I wanted to retrigger it.

== What happened:

There is no "retrigger" link. I am confused!! Turns out it is hidden because this job has already been retriggered by someone else! They beat me to it.

== What I expected to happen:

The page should show an inactive (grayed-out) "retrigger" link with the additional text "(already retriggered and pending)" after it to make clear what the current status is.

---
Originally reported by peterp, imported from: job shouldn't completely hide "retrigger" link when new build is pending


  • status: Open
  • priority: Minor
  • component(s): gerrit-trigger-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 2
  • imported: 2025-12-06

Raw content of original issue

We have a setup where Gerrit triggers a job in Jenkins. When the build fails, normally there is a "retrigger" link on the left of the page to retrigger the build to happen again.

== What I did:

Navigated to the build page for this job because I wanted to retrigger it.

== What happened:

There is no "retrigger" link. I am confused!! Turns out it is hidden because this job has already been retriggered by someone else! They beat me to it.

== What I expected to happen:

The page should show an inactive (grayed-out) "retrigger" link with the additional text "(already retriggered and pending)" after it to make clear what the current status is.

Contributor guide

Open the contributing guide

Research direction

Start by locating the gerrit-trigger-plugin implementation of the build-page "retrigger" link and the logic that hides it while a new build is pending. Check for existing tests around retriggering, then make the pending state visible with an inactive link and the requested explanatory text.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.