|
||||||||
|
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.
I think you've misunderstood what it is saying. The git plugin and the git client plugin support Jenkins versions 1.509 and later. Those plugins are actively used at many sites with Jenkins versions newer than 1.509, including 1.532 and 1.565.*. I use the plugins heavily at two different locations that I manage. It doesn't fail in general with newer Jenkins.
I think there is something specific either about the steps you took, compared to others.
For example, if you disabled the git client plugin without disabling the git plugin, then your Jenkins was in an inconsistent state. It would be good for the Jenkins core to present a better message for those types of inconsistencies, but it is an inconsistency which the plugin itself is not able to repair.