|
||||||||
|
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.
I believe you have misunderstood what you are sacrificing by staying with an outdated version of a critical part of the Jenkins process.
Nicolas noted that credentials support is not available in that git version. Substantial work has been put into the git and subversion plugins to support credentials. It may not be relevant to you, but it is relevant to the larger community of Jenkins users.
If you are unwilling to update git, then you could evaluate the recently added JGit support. It is not yet full featured, but when a feature is missing it will generally tell you clearly that the feature is missing.
If neither of those meet your needs then you will probably need to pin an older version of the git plugin and accept that the new features won't be available to you.