|
||||||||||||||
|
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/groups/opt_out.
Considering the already complex workflows available from the Git plugin and the Git client plugin, and the availability of the Subversion plugin for Jenkins, I'm marking this as "Won't fix".
I think it would not be helpful to add even more complexity to the Git plugin workflow (how to configure git svn, how to recover when git svn has a problem, etc.).