Mark Waite commented on Bug JENKINS-27677

Unfortunately, I don't think there is much you can do to change that (at least for me). Sorry about that. I think the investigation work will need to come from you.

I can't duplicate your problem.

I don't have a FreeBSD system in my git plugin / git client plugin test environment (only Windows 7 x86, Windows 7 x64, Windows 8.1 x64, Windows Home Server 2011 x64, Debian 6 x86, Debian 7 x64, Debian 8 x64, Ubuntu 14.04 x64, CentOS 6 x86, and CentOS 7 x64).

I don't have a GitLab server in my test environment (only GitHub, gitweb, bitbucket, sourceforge, and a few others).

I'm a volunteer who contributes to the plugins on my personal time, so you'd need to persuade me to use my personal time to work on a problem which I can't duplicate, and which has hints that it may be related to a local configuration problem. Some of the things I find most persuasive are things like:

  • Expand the understanding of the platforms where the bug happens and does not happen, so that its impact to the larger community is more clear. If, for example, the problem also appears when using GitHub or bitbucket or a git protocol server on CentOS or Debian, that makes it more interesting to me
  • Expand the understanding of the versions where the bug happens and does not happen, so that its impact to the larger community is more clear. If, for example, the problem also appears when using the most recent long term support release, that is more interesting to me, since I'm a user of the long term support release
  • Expand the understanding of the conditions where the problem happens and does not happen, so that its impact to the larger community is more clear. If, for example, the problem does not appear when using git plugin 2.3.4 and does appear in 2.3.5, then that is very interesting, since it hints that there was a plugin version which behaved more the way you wanted

If you'd rather have a more direct form of persuasion, you might be able to persuade others to investigate the problem by paying them to investigate. There is also freedomsponsors.org which provides a way to offer to fund a bug fix or investigation. I don't think my employer will allow me to take money for my personal development activities, so neither of those techniques will persuade me. It's not a personal thing, nor is it me saying that the problem you've found is not a bug.

I hope that my description is not viewed as an attempt to offend or rebuff your concern. It is not. I'm trying to help you see which things might persuade others to help, and which will not.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to