• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Component/s: core
• Labels:

  • api
  • exception
  • rest
• Environment:

  https://ci.jenkins-ci.org/ running Jenkins ver. 1.565-SNAPSHOT (rc-05/20/2014 18:32 GMT-kohsuke)

1. 

   2014-10-13_21h54_14.png

   113 kB

   2014-10-13 20:13

2. stack-trace.txt

   8 kB

   2014-10-13 20:13

[JENKINS-25132] Remote access API - listing culprits using the 'tree' query parameter throws exception

Collapse comment: Daniel Beck added a comment - 2014-10-13 20:49

Daniel Beck added a comment - 2014-10-13 20:49

If this were related to the newest build, wouldn't https://ci.jenkins-ci.org/job/jenkins_rc_branch/468/api/xml?tree=culprits fail?

Expand comment: Daniel Beck added a comment - 2014-10-13 20:49

Daniel Beck added a comment - 2014-10-13 20:49 If this were related to the newest build, wouldn't https://ci.jenkins-ci.org/job/jenkins_rc_branch/468/api/xml?tree=culprits fail?

Collapse comment: Daniel Beck added a comment - 2014-10-13 20:56

Daniel Beck added a comment - 2014-10-13 20:56

Appears to duplicate JENKINS-16737.

The problem with reporting bugs in someone else's instance is that you have no way to help the investigation by providing non-public data, and no way to verify a fix. IOW, these issues are usually a dead end.

(OTOH if you're specfically reporting issues with the Jenkins Project infrastructure, the INFRA project may be a better place.)

Expand comment: Daniel Beck added a comment - 2014-10-13 20:56

Daniel Beck added a comment - 2014-10-13 20:56 Appears to duplicate JENKINS-16737 . The problem with reporting bugs in someone else's instance is that you have no way to help the investigation by providing non-public data, and no way to verify a fix. IOW, these issues are usually a dead end. (OTOH if you're specfically reporting issues with the Jenkins Project infrastructure, the INFRA project may be a better place.)