[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access

[so...@linux2go.dk (JIRA)]

Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access This seems to have been introduced by https://github.com/jenkinsci/jenkins/commit/5548b5220cfd496831b5721124189ff18fbb12a3 This makes it work again: https://github.com/sorenh/github-oauth-plugin/commit/da5c787cf72580f06c6a6318bf1b8a73071e8bcd But I'm fairly sure it's not the right fix: The correct fix should be to make sure the authtoken is set. I don't know why it isn't. The correct exception to throw in that situation seems like DataAccessException, but that would not actually make this work again. Perhaps someone else can shed some light on why authtoken might be null at this point? I've never looked at Jenkins internals before (and haven't really touched java in around a decade), so any further input would be greatly appreciated.

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.