|
||||||||
|
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.
You could try toggling the value of the git plugin additional behavior "Use commit author in changelog" to see if that reduces the frequency of the issue.
I've seen instances where the git plugin incorrectly throws the "No author in changeset" exception, even without the MultiSCM plugin. I haven't found specific conditions which cause it repeatably, but have definitely seen it, and have seen that after a build or two, the problem seems to "hide itself" again.
I think it is a bug in the git plugin that it should not throw a RuntimeException when an author cannot be extracted from a changeset. I don't think the author is critical enough to the operation of the plugin to justify failing a build if the parsing fails.