|
||||||||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Thanks for participating with the Jenkins project.
Please use the Jenkins users mailing list for questions, rather than submitting a bug report. The mailing list is monitored by many more people than monitor the bug report database, and there is a much better chance that someone will be able to help you.
If after discussing your question on the mailing list, you decide that it truly is a bug, then you will need to provide much more information than a stack trace. You also need to submit it to the correct component so that the maintainer of that component will be able to find the bug report.
Refer to "How to report an issue" for helpful hints on information which will improve the chances of someone investigating the bug.
There is no indication in this bug report that the problem has anything to do with the git client plugin, so I closed it as "Not a defect". If you have additional information that shows it is a problem with the git client plugin, please include that with the bug report and either reopen it, or create a new bug report.