We are now back on 1.1.21 and the problem appears to have been eliminated. Our test environment will be set up with 1.1.26 next week.
On Thu, Feb 14, 2013 at 11:15 AM, nicolas de loof <[email protected]>wrote: > > 2013/2/14 Don Ross <[email protected]> > >> I can confirm that our build jobs, and our build environment, has not >> changed in several weeks. We saw the behavior almost immediately after >> upgrading both the Jenkins server to 1.480 (from 1.1478) and the Git >> plug-in to 1.1.26 (from 1.1.21), and nothing else changed at that time. >> Today we are rolling back the plug-in and, if the problem goes away, that >> will confirm the plug-in is to blame. >> >> Which version of git plugin are you running now ? > > >> Unfortunately, I don't have the infrastructure, nor the expertise, to >> build my own version of the plug-in from source, and my hypothesis is pure >> speculation in case the suggestion rang a bell with you. We could try to >> apply incremental upgrades of the plug-in over time, but since this is in a >> production environment, it will take a week to vet each upgrade. We are >> trying to reproduce the problem in a test environment, which will give us >> more flexibility. > > > Sure, first thing to do. Then I can help you to create snapshots of the > plugin to isolate the commit to introduce this regression. > >> >> >> On Wed, Feb 13, 2013 at 8:46 AM, nicolas de loof < >> [email protected]> wrote: >> >>> This is not a trivial one to debug. >>> Could help if you can confirm previous git plugin version was ok in same >>> environment, and then maybe to confirm your hypothesis to build a custom >>> git plugin that reverts the "merge targets" support >>> >>> as a general answer to the issue you see logged in Jira, I'd like to >>> refactor the plugin to use JGit in replacement for git cli ran as a system >>> command, so that it don't rely on an external process, fragile output >>> parsing, etc >>> >>> >>> 2013/2/13 Don Ross <[email protected]> >>> >>>> 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 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. >> >> >> > > -- > 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.
