Samy Lerari commented on Bug JENKINS-21181

Got the exact same exception after simutanously upgraded Jenkins to 1.545 and Build Pipeline Plugin to 1.4.2.

All non admin users who had only Global Read permission (plus of course some job level permissions) had this exception. I was forced to give them global read+discover permission which resulted on all users seeing all jobs.

Corrected the issue by downgrading Build Pipeline Plugin from 1.4.2 to 1.4.1. Switched back to only Global Read permission : users now only see jobs they can interact with (and no longer all of them).

Note : This seems to me duplicate of 20993

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to