|
||||||||
|
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/d/optout.
I found the cause for the errors:
08/01/2014 10:00:27 Archiving artifacts
08/01/2014 10:00:27 FATAL: No author in changeset 506fc54deb5c89c43450dc60a054159999198b0atree
08/01/2014 10:00:27 java.lang.RuntimeException: No author in changeset 506fc54deb5c89c43450dc60a054159999198b0atree
08/01/2014 10:00:27 at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:336)
This is caused by a change in the Multiple SCMs Plugin that changed the format of the changelog.xml that it creates. The Git Plugin is parsing the chagelog.xml as a normal text file and not as an XML file. The Multiple SCMs Plugin version 0.3 started to HTML escape the "<>" around the email address of the author and committer in the git change log which broke the parser in the Git Plugin.
For example in a failing changelog.xml
with the 0.3 Multiple SCMs Plugin we have:
<multi-scm-log>
<sub-log scm="hudson.plugins.git.GitSCM">
<![CDATA[commit 67be86f982e16ef56a6efaede836f0e9619c95f1
tree fb60b7ae44641004d799d0a6d2d38f377ea59d55
parent d1ff9a84aaaed6d2e6ab6116b887ab80dc959120
author myuser <[email protected]> 1398272644 -0400
Since the <> are being escaped the Git Plugin parser is not able to find the author.
With the old plugin the "<>" weren't escaped:
<multi-scm-log>
<sub-log scm="hudson.plugins.git.GitSCM">
<![CDATA[commit 67be86f982e16ef56a6efaede836f0e9619c95f1
tree fb60b7ae44641004d799d0a6d2d38f377ea59d55
parent d1ff9a84aaaed6d2e6ab6116b887ab80dc959120
author myuser <[email protected]> 1398272644 -0400
Since the changelog.xml is an XML formatted file shouldn't the parser in the Git Plugin use an XML parser to retrieve the contents of the <sub-log> tag.
So reverting back to the 0.2 Multiple SCMs Plugin fixed this for me.