I concur with Stephen and Nicolas about this being a community effort and commend them for their contribution and for the help of their employer.
I think the community may have already discovered a variant this problem and has already provided a fix for some of the cases. That fix has already been pulled into the source code of the git-plugin through a community contribution. It has not yet been released in a new version of the git plugin. If your git configuration for this job does not define any exclusion regionss, does not define any excluded committers, and does not define any inclusion regions, then the next release of the git plugin (whenever that happens) will resolve your issue. Refer to https://github.com/jenkinsci/git-plugin/commit/81f432ef0961149b13ff82d7803a897587d8c887 for the details of the commit. Thanks, Mark Waite I agree with Stephen and Nicolas that enterprise support is available from their employer (I suspect that is CloudBees). There were a number of interesting discussions about the inherent problems in the "git show" command and its use in the git plugin. As far as I can tell, this is the one and only use of the "git show" command, and it can be avoided in most cases (with the change mentioned above). >________________________________ > From: Stephen Connolly <[email protected]> >To: "[email protected]" <[email protected]> >Sent: Wednesday, February 13, 2013 7:18 AM >Subject: Re: Support for git plug-in? > > >On 13 February 2013 13:36, Don Ross <[email protected]> wrote: > >I am sorry, this is my first foray into trying to get support for a >community-maintained tool. We are using Jenkins in an enterprise environment > > >[My & Nicolas' employer's hat] > > >If you were/are a paying customer of My & Nicolas' employer's you could/can >apply whips and chains to Nicolas to get the bug fixed > > >(Nicolas, no cheating and assigning to me ;-) ) > > >[/My & Nicolas' employer's hat] > > >Sorry, I couldn't help myself there... I did remove the name of My & Nicolas' >employer, though it isn't exactly a secret. > >and haven't had any issues we couldn't solve ourselves since I started working >here. Thanks for getting back to me directly. >> >>My issue is reported as https://issues.jenkins-ci.org/browse/JENKINS-16693; >>basically, we are getting heap errors since upgrading to the latest plug-in >>version, but only in our production environment. We can't reproduce it in >>the supposedly-identical test environment or we wouldn't have upgraded. I >>think it is due to the enhancements made in version 1.1.23 to changelog >>parsing for merge targets, but that is just speculation on my part. >> >>Any debugging suggestions you have would be welcome. >> >>Thanks, >>Don >> >> >> >>On Wed, Feb 13, 2013 at 8:21 AM, nicolas de loof <[email protected]> >>wrote: >> >>yes it is, but filling a bug (which one ?) doesn't mean someone will jump on >>it to fix. This is a community effort :P >>>issues are by default assigned to plugin maintainer (me) so the status on >>>jira. I don't really monitor it (my bad), as I mostly focus on my own issues >>>with this plugin and contributors pull-requests. >>> >>> >>>2013/2/13 <[email protected]> >>> >>> >>>Is the Git plug-in still supported? I filed a bug issues.jenkins-ci.org >>>last week and haven't seen any movement on it, or on any of the issues filed >>>in the last six months against the Git component. There are about fifty >>>such issues, most of them assigned to Nicholas de Loof (the original author, >>>I think), and none of them with any response or acknowledgement from him (or >>>anyone else). >>>> >>>>-- >>>>You received this message because you are subscribed to the Google Groups >>>>"Jenkins Developers" 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/groups/opt_out. >>>> >>>> >>>> >>> >>> -- >>>You received this message because you are subscribed to the Google Groups >>>"Jenkins Developers" 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/groups/opt_out. >>> >>> >>> >>-- >>You received this message because you are subscribed to the Google Groups >>"Jenkins Developers" 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/groups/opt_out. >> >> >> > -- >You received this message because you are subscribed to the Google Groups >"Jenkins Developers" 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/groups/opt_out. > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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/groups/opt_out.
