|
||||||||
|
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.
A failing permission check showing a warning could be acceptable - as it could suggest the 2 solutions (add built root token or allow anon read access). Even the text of it changing to emphasise that it won't work on secured jenkins (by default) with suggestions would also be good.
A variation of the 1st one if to just include the build toot token action in core https://github.com/jenkinsci/build-token-root-plugin/blob/master/src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java - a 100 odd lines - vs having it as an optional plugin (users can then be encouraged to use that url if they need access from outside).
I would prefer the latter as a permission check doesn't have to be performed - we can just direct people to use the parametrised root path. Everything existing would work as is.