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] <javascript:>> 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 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.
