Removed integrity-plugin as this is not a integrity-plugin problem and should be fixed in multi-scm.

Change By: Tyrel Alastair Hunter (26/Dec/13 6:14 AM)
Summary: Integrity Plugin does not generate changelog when used with multiple-scms plugin Child SCM's include CDATA sections
Assignee: Cletus D'Souza Tyrel Alastair Hunter
Description: When using  the integrity-  a SCM plugin  with the multiple-scms plugin integrity-plugin detects  that  a database exists already during  has CDATA inside  the  checkout process  xml the multi-scm changelog becomes invalid xml .  It then proceeds  Any data inside the multi-scm changelog should be xml escaped prior  to  delete this database and create a new one for  writing it to  the  second project  file .  Since this DB  Also when the file  is  used to generate  split  the  changes for jenkins. It  data  should  not  be  deleted  un-escaped so that it is valid for the child SCM plugin .
Component/s: integrity-plugin
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to