|
||||||||
|
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.
We are not likely to bundle additional plugins in core. Lots of things are considered obviously essential by some people, and just result in a shrug from others.
Your second option does not work as written since core build tokens work fine when security is configured, so long as the anonymous user is granted read permission, which is quite common. It would have to actually run a permission check against the current job while impersonating anonymous. Anyway when this check fails, I think it should not hide the checkbox, it should just display a form validation warning explaining the situation and pointing out the existence of BTR. (In fact you still need the checkbox visible since BTR still relies on the core token configuration. The warning could be suppressed when BTR is installed, since presumably you are then using it.)