jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-16896] per-project permissions for gerrit triggering of patches

Open
#620 0 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

At the moment Jenkins allows per-project permissions to be set for the "Build Now" functionality.

With a gerrit-trigger based workflow the permission to allow forcibly triggering a project is set at a global level but not at a project level meaning that users with the permission can trigger projects that do not belong to them. This should be fixed.

---
Originally reported by liamjbennett, imported from: per-project permissions for gerrit triggering of patches


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

Raw content of original issue

At the moment Jenkins allows per-project permissions to be set for the "Build Now" functionality.

With a gerrit-trigger based workflow the permission to allow forcibly triggering a project is set at a global level but not at a project level meaning that users with the permission can trigger projects that do not belong to them. This should be fixed.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.