|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I'm having the same problems and saw similar problems with Atlassian's Stash and Fisheye when they moved to jgit. There was some horrible / stupid hacks that I had to do to get it to work. I would vote not using jgit as this was working properly before. For as long as I have used Jenkins + Git (+5 years), I have never experienced a problem with the old implementation. If you are seeing memory / output problems, it's probably not from Git.