[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
David Ishee commented on JENKINS-15309 NPE (isEmpty) from main.groovy I manually re-entered all my jobs. You can close this issue if you want to. 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.
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
David Ishee commented on JENKINS-15309 NPE (isEmpty) from main.groovy I updated to Jenkins 1.480.1, and set the security realm to Active Directory, and Authorization = "Anyone can do anything". It didn't change the error message. I changed the Authorization to "logged in users can do anything", but the error message is still there. The Anonymous View works OK. 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
David Ishee commented on JENKINS-15309 NPE (isEmpty) from main.groovy A lot of other problems are showing up. I think I'm going to give up on trying to upgrade a Hudson installation and start with a clean Jenkins install and re-do all my jobs. It looks like that is the only workable solution. 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra commented on JENKINS-15309 NPE (isEmpty) from main.groovy What about authenticated? Do you have the JOB: DISCOVER permission set there? If so, try removing it 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra commented on JENKINS-15309 NPE (isEmpty) from main.groovy I've seen this happen when Anonymous was granted the JOB:discover permission (Project-based Matrix Authorization Strategy) Removing the check-mark resolved it 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra edited a comment on JENKINS-15309 NPE (isEmpty) from main.groovy I've seen this happen when Anonymous was granted only the OVERALL: Read JOB:discover permission Selecting both JOB: READ DISCOVER permissions resolved the issue or removing the discover altogether also resolved it. (Project-based Matrix Authorization Strategy) 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra edited a comment on JENKINS-15309 NPE (isEmpty) from main.groovy I've seen this happen when Anonymous was granted only the OVERALL: Read JOB:discover permission Selecting both JOB: READ DISCOVER permissions resolved the issue or removing the discover altogether also resolved it (but then users get the 404 error when accessing a job from a URL) (Project-based Matrix Authorization Strategy) 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Jesse Glick updated JENKINS-15309 NPE (isEmpty) from main.groovy Change By: Jesse Glick (15/Oct/12 7:06 PM) Summary: StatusCode:500error NPE(isEmpty)frommain.groovy 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Jesse Glick commented on JENKINS-15309 NPE (isEmpty) from main.groovy Some View.getItems call is returning null for some reason. Hard to say what that reason is without knowing what page you were viewing when you got this exception, what the default view was configured to be in Hudson, and what errors might have preceded this in your log file. 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
David Ishee commented on JENKINS-15309 NPE (isEmpty) from main.groovy What can I do to help you debug this? I can provide more info if you direct me to what you need. 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Jesse Glick commented on JENKINS-15309 NPE (isEmpty) from main.groovy If you can run a Java debugger, set a breakpoint on impls of View.getItems. Otherwise, record the URL producing this exception, your log file, and the views section of $JENKINS_HOME/config.xml. 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
