|
||||||||
|
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/d/optout.
We're still running 0.14 until this is fixed. I tried rolling back to 0.16 after updating to 0.19 and it did not fix the problem.
Can we please see this as a priority item for 0.20 ?
Until a fix for this is in place, no other improvements to the plugin are meaningful. Anyone who doesn't want this kind of access (which is everyone, btw) and cares (should be everyone, but isn't) is forced to use old versions.
More complex access control would be great, sure, but not making Jenkins into a giant security hole is a much higher priority.