|
||||||||
|
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.
I upgraded another Jenkins server to 1.544. It now gets the same : org.apache.commons.jelly.JellyTagException. This other server is using Active Directory authentication with Project-based Matrix Authorization Strategy.
This issue is now reportedly occuring with LDAP authentication with Project-based Matrix Authorization Strategy, Active Directory authentication with Project-based Matrix Authorization Strategy, and Unix user/group database athentciation with Project-based Matrix Authorization Strategy.
Seems pretty clear the root cause is not related to an authentication strategy, and probably via use of "Project-based Matrix Authorization Strategy." In both my servers experiencing this bug, giving Admin credentials to people (either individually or through authenticated group, or via anonymous user) all allows them to login without error.
This problem defintitley happened for us, immediately after upgrading to 1.544. (along with a slew of plugins) We upgraded from 1.517 to 1.5444. Incidentally, rolling back just jenkins.war to 1.517 did not cause the problem to go away (although the presentation of the stack trace screen was slightly different) which seems to indicate one of the plugin upgraded is the culprit.