By 'this', I was referring to the email exchange I was having with Mr. Deloof about debugging JENKINS-16693 in my environment, in the hopes of helping him find a solution for this problem which seems to be effecting many users (as there are multiple similar bugs filed in the issues-jenkins-ci in addition to mine).
I am not in a position to submit a pull request as that would require expertise of which I am rather lacking, which is one of the reasons I prefer to use third-party tools over home grown. However, if an effort was being made in the community to resolve the defect, I can participate by providing a production test environment. Respectfully, Don. On Mon, Mar 18, 2013 at 6:19 PM, Mark Waite <[email protected]> wrote: > Can you clarify what you intend by "this"? > > If "this" is https://issues.jenkins-ci.org/browse/JENKINS-16693 (as > mentioned in the beginning of the thread), then the problem is that the Git > plugin isRevExcluded() method uses "git show" to decide if commits since > the last build should be excluded or not. The "git show" command can > generate massive amounts of output and the isRevExcluded() method is not > designed to handle the large volume output from "git show". If you want to > submit a pull request for an alternate implementation of isRevExcluded > (preferably with many more tests to confirm it works in many more cases), > I'm sure the plugin maintainer would be willing to consider your pull > request. > > Thanks! > Mark Waite > > > On Monday, March 18, 2013 11:59:23 AM UTC-6, Don Ross wrote: > >> W have managed to replicate this issue in our test environment, and >> confirmed it still exists in the all-new version 1.3.0. >> If you have suggestions for things I can try to further diagnose the >> issue, I am eager to once again engage in resolving this. >> >> On Fri, Feb 22, 2013 at 12:37 PM, <[email protected]> wrote: >> >>> Now that we are no longer blocked, this has dropped to the bottom of the >>> queue for the RelEng department. I am still pressuring them for >>> resolution, because if this is not a real problem with the plug-in, then we >>> must be using Git in some non-standard way that causes unexpected behavior >>> and I would like to change that. >>> >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/82KcytLyMwA/unsubscribe?hl=en > . > To unsubscribe from this group and all its topics, 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.
