-
Bug
-
Resolution: Unresolved
-
Minor
In some of our jobs, the build result page gets some text appended using a Groovy postbuild step. The appended text can contain arbitrary characters, even an escape character (character code 27). Everything works fine.
On accessing such a build via XML api, there is an exception because the XML output contains invalid characters:
error on line 1 at column 9913: PCDATA invalid Char value 27
I'm aware that I can avoid this issue by filtering the appended text in the groovy step, but generally the XML API should filter or escape such invalid characters from the output.
[JENKINS-22566] XML API does not escape/filter invalid characters
Michael Keppler
created issue -
| Labels | New: stapler |
| Workflow | Original: JNJira [ 154669 ] | New: JNJira + In-Review [ 178883 ] |
Basil Crow
made changes -
| Remote Link | New: This issue links to "Reproducible test case (Web Link)" [ 22334 ] |
Basil Crow
made changes -
| Assignee | New: Basil Crow [ basil ] |
Basil Crow
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Basil Crow
made changes -
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Basil Crow
made changes -
| Remote Link | New: This issue links to "jenkinsci/jenkins#5654 (Web Link)" [ 26841 ] |
Basil Crow
made changes -
| Remote Link | New: This issue links to "stapler/stapler#248 (Web Link)" [ 26842 ] |
| Labels | Original: stapler | New: stalled-pr stapler |
Basil Crow
made changes -
| Assignee | Original: Basil Crow [ basil ] |