|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
The downside of this change is that if you update permissions and start referencing a new group, people need to log out and come back into to see the effect.
I think the performance improvement is great, and I get that this is a practical fix to work around the problem at hand for the author, but at the same time, I feel that this is exposing a complexity to users, when a problem should have been solved by us.
Role-based Authorization Strategy plugin has known performance issues, and as for the matrix auth plugin, I think SparseACL.hasPermission() implementation should be improved to reject uninteresting {{Sid}}s more quickly.