[JENKINS-8566] Don't allow to build job without being through the trigger

It is not immediately apparent to some users that jobs configured to use the hudson trigger should not be built outside of the trigger (i.e. by clicking Build Now on the job page), since that won't provide the proper parameters. Is there any way to remove that button, forcing users to dig deeper and find the Query and Trigger Gerrit Patchsets functionality, instead of kicking off a job that's doomed to fail, with little reason why it failed.

---
Originally reported by ccutrer, imported from: Don't allow to build job without being through the trigger

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

It is not immediately apparent to some users that jobs configured to use the hudson trigger should not be built outside of the trigger (i.e. by clicking Build Now on the job page), since that won't provide the proper parameters.  Is there any way to remove that button, forcing users to dig deeper and find the Query and Trigger Gerrit Patchsets functionality, instead of kicking off a job that's doomed to fail, with little reason why it failed.

Start by locating the Jenkins job-page action that exposes Build Now and the gerrit-trigger configuration that supplies required parameters. Determine how manually initiated builds can be prevented for jobs using this trigger, then verify that the Gerrit query and trigger flow still works and that the failing manual path is no longer available.

Written by the indexing model from the issue text.