|
||||||||
|
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.
And that makes sense - once Jgit is up to the challenge. Judging by the number and age of the currently open bugs against Jgit I have to question its current stability but I'm sure eventually it'll be made to work as well or even better than native git despite the shortcomings of doing git in Java (this very bug reflects the fact that Java takes a lot of coaxing (and external hooks) to work seamlessly at a low level with a given operating system and its filesystem structures).
As for dependencies, it appears Jgit requires extensive backward compatibility with various flavors of Java. Looks like it's just trading one kind of fragility for another right now.
This isn't the place for a discussion of the merits of this change, other than to suggest that such a fundamental change get more visibility when it happens. I certainly didn't expect a minor point release of Jenkins to make this large of a change.
I'll monitor the new Jgit bugs closely before we commit to updating to future point releases, and I'll let you know once we've tested this patch. Does this patch fix any other issues due to Jgit in Jenkins or just this one?