[JIRA] (JENKINS-14537) Template SCMs + Multiple SCMs results in failure parsing change log

[jhans...@myyearbook.com (JIRA)]

Joe Hansche commented on JENKINS-14537 Template SCMs + Multiple SCMs results in failure parsing change log To elaborate, I think the problem is that ProxySCM should avoid the CDATA entirely, because it should be understood that the remote ("proxied") SCM will already use CDATA where it needs to: <multiple-scms> <sub-log scm="hudson.plugins.git.GitSCM"> <![CDATA[Changes in origin/master, ... ... ...]]> </sub-log> <sub-log scm="hudson.plugins.templateproject.ProxySCM"> <sub-log scm="hudson.plugins.git.GitSCM"> <![CDATA[Changes in projectA/master, ... ... ...]]> </sub-log> </sub-log> </multiple-scms> That way, even if ProxySCM uses only a single remote GitSCM configuration, it is still valid. I haven't looked into the code, so the problem may actually be Multiple-SCMs using CDATA all the time, when it is only necessary for the actual final SCM log data. That may be difficult to determine though, since neither plugin was probably designed to work with the other. In our case though (as mentioned in the Environment field above), this combination is actually very useful, and we use it for dozens of jobs. It works well in general, the only thing that fails is the changelog parsing (which in turn causes our log file to fill up because of the error in parsing the changelog.xml 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