In Jenkins 2.462.1, following the recent security advisory (Jenkins Security Advisory 2024-08-07), the ability to view other users’ build views has been removed. This change has impacted how our teams monitor their builds.
Our Setup:
- Each team leader previously created build monitors or views relevant to their team, which were then shared within the team.
- We have multiple teams using the same Jenkins instance, and multiple teams are interested in the same jobs.
No optimal alternatives:
- Global Views: We could create global views at the root level, but this requires users to have permissions to create views at the root, which isn’t ideal. Our jobs are managed via JobDSL or Organization Folders, so users don’t directly create jobs in Jenkins.
- Folder-Based Views: We considered creating a folder with “project permissions,” but this approach only allows viewing jobs recursively down the folder structure, not up.
- Team user: Setup a specific team user with shared credentials.
Question: Has anyone found a solution for creating team-specific dashboards or build views in Jenkins that can be managed by the team without granting them extended permissions? Any suggestions or best practices would be greatly appreciated!