Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339013 - [upstream][jenkins][hudson] Unexpected error: Element type "origin"
Summary: [upstream][jenkins][hudson] Unexpected error: Element type "origin"
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 0.7   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL: http://issues.jenkins-ci.org/browse/J...
Whiteboard:
Keywords:
Depends on:
Blocks: 357679
  Show dependency tree
 
Reported: 2011-03-05 14:08 EST by Brendon CLA
Modified: 2011-09-14 16:01 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brendon CLA 2011-03-05 14:08:15 EST 
using version 0.7.0.I20110305-0336 with mylyn version 3.5.0.I20110305-0336

It detects my jenkins server (1.3999) fine but refreshing the build status or trying to look at a build gives me the following error.

Refresh of server 'homeserver' failed
Unexpected error: Element type "origin" must be followed by either attribute specifications, ">" or "/>".
Element type "origin" must be followed by either attribute specifications, ">" or "/>".

Running a build works, it gives me the same error but actually does run the build

The history view works at displaying all the builds but doesn't let you see the details.
Comment 1 Steffen Pingel CLA 2011-03-05 17:05:24 EST 
Thanks for the report. I am able to reproduce this with ci.jenkinks-ci.org. I'll look into it.
Comment 2 Steffen Pingel CLA 2011-03-05 17:14:40 EST 
Looks like Jenkins produces invalid XML when you open http://ci.jenkins-ci.org/job/gerrit_master/lastBuild/api/xml for instance:

XML Parsing Error: not well-formed
Location: http://ci.jenkins-ci.org/job/gerrit_master/lastBuild/api/xml
Line Number 1, Column 168:

...  <buildsByBranchName><origin/master><buildNumber>

The / is not valid in the element name. This needs to be fixed on the server side. Can you report this problem to the Jenkins project directly?
Comment 3 Brendon CLA 2011-03-05 17:33:33 EST 
looks like it has been reported 
http://issues.jenkins-ci.org/browse/JENKINS-8855

should i close this issue?
Comment 4 Steffen Pingel CLA 2011-03-05 20:55:39 EST 
Thanks for the link. I'll mark this bug as resolved. Hopefully it will be fixed in Jenkins soon.
Comment 5 Steffen Pingel CLA 2011-08-12 12:03:20 EDT 
Unfortunately Hudson now has this problem: http://issues.hudson-ci.org/browse/HUDSON-8838 .