Pushing multiple branches to a single repository with merge commits causes Unmarshal/SAXParse exceptions

Issue #807 new
created an issue

We consistently have a user that is doing a normal pull from default into some dev and RC branches, merge default to a dev branch, merge dev to RC, merge RC to dev, then making a couple changes in each branch that get committed, then push these changes to the server.

On the server side, probably 1/8 of the time that this workflow is used, we get a stacktrace where the webhook plugin (HookChangesetBuilder) is trying to read the repository's XML, runs into a spot where one of the sets of changes is still writing (ie unclosed tags) and then blows up.

It appears that if the webhook waited for an event from the repository that it was OK to send an event this might not happen.

Comments (0)

  1. Log in to comment