Details
-
Improvement
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
Description
The current implementation of XmlFile.java emits an XML 1.0 header, which breaks things like Move/Copy/Promote if the user has included any characters that are illegal in XML 1.0 (such as Control-XX, etc) in their jobs.
XStream, which is used for serialization/deserialization, deals with XML fragments, and doesn't have an issue reading/writing this non well-formed XML. Changing XmlFile.java so that it creates xml 1.1 here will allow jenkins config files to support these special characters. This also requires updating the underlying XML Pull Parser being used by XStream to something that support XML v1.1
Attachments
Issue Links
- relates to
-
JENKINS-54146 Job History Plugin 2.18.2 - XML view not working
-
- Resolved
-
-
JENKINS-50358 While downgrading Jenkins version 2.112 to 2.101 getting eror
-
- Resolved
-
- links to
If the config.xml file format is considered internal, Jenkins shouldn't have APIs that expose it. That's not internal.