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 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.
