Hi Mark,
Thanks a lot for the detailed responses. After banging my head against a
brick wall for so long, I'm actually just happy to have the correct answer
- and it is correct. I changed the password for our user to something not
using those types of characters, and now the authentication is
There is one other alternative (referenced in the serverfault posting from
"bobs"), though I don't recommend it. If your Jenkins server is purely
Windows based, and never has any agents ("slaves"), then you might be able
to configure the git credentials manager on Windows to always answer the
If you choose to help evaluate the pull request, you can download the
latest build from my evaluation branch at
https://drive.google.com/open?id=0B9GyYWyfT1N5Y1NPS1hnbU13elk . That is an
unreleased build of the git client plugin which includes the Windows
password escaping change.
Mark Waite
On
You can't change the Jenkins git client plugin from using ASKPASS to using
.gitcredentials. The plugin does not have selectable password prompting
methods.
It used .gitcredentials in releases prior to 2.0, and switched to ASKPASS
in releases 2.0 and later. That change was made so that submodule
au
I'm trying to upgrade our Jenkins to 2, but coming accross a problem with
git authentication. I've got Git credentials loaded and they currently
work, but when I upgrade the plugin from 1.19.6 to 2.1.0, all jobs that use
Git for SCM fail with the same error message. As soon as I downgrade the
