Still presented on git 2.3.5 and git-client 1.17.1. Jenkins 1.609.

I am also receiving this error git plugin version 1.68 Jenkins version 1.617.

I can see this error when configuring the job
Failed to connect to repository : Could not init C:\Windows\TEMP\hudson1802685872087768658tmp

Also when running the job: > C:\Program Files (x86)\Git\bin init C:\Program Files (x86)\Jenkins\jobs\WebServices\workspace # timeout=10
ERROR: Error cloning remote repo 'origin'
ERROR: Error cloning remote repo 'origin'
Finished: FAILURE

Code changed in jenkins
User: Mark Waite
Path:
src/test/java/org/jenkinsci/plugins/gitclient/CredentialsTest.java
http://jenkins-ci.org/commit/git-client-plugin/ff9c219277531dcf0f18dccd6d8665118e1827a3
Log:
Add username/password support to CredentialsTest

Help test JENKINS-26757, JENKINS-24368 and JENKINS-28460.

A fix from Jacob Keller for JENKINS-29604 in the latest git-client-plugin 1.18.1 pre-release has fixed this so that a username / password credential works correctly with a bitbucket private https URL like https://markewaite@bitbucket.org/markewaite/bin.git.

A username / password credential does not yet work with a bitbucket private URL when that URL is using the ssh protocol, like git@bitbucket.org:markewaite/bin.git . In order to use ssh protocol with the git protocol, a private key credential is required, rather than a username / password credential.

Thanks for checking. I had run that test interactively and thought it worked. An automated test is definitely working in my test harness. Unfortunately, when I just attempted the same thing from a fresh docker instance of Jenkins using https://username:password@bitbucket.org/username/private-repo.git, it failed. I then used the same repository URL from command line git and confirmed it works correctly.

The automated test must not be matching the real world closely enough. I'll explore further as time allows.

This seems to work fine now. Just add the URL e.g. https://bitbucket.org/owner/repo.git and select a username+password credential.

Jenkins 2.138.1, Git client plugin 2.7.3, Git plugin 3.9.1, Credentials Plugin 2.1.18

Thanks jameshowe! The specific case that was failing for me did not use a Jenkins credential. It embedded the username and password into the URL as in:

 https://username:password@bitbucket.org/username/private-repo.git

I suspect that case may still be broken. I believe it is a largely irrelevant case, but it was not well-behaved the last time I checked (3 years ago). I have a test in my regression kit that is known to fail with that case. I haven't run that known failure test in quite a while.

markewaite no, that works too AFAICT. Though obviously not a great way to do it, as your password is then in plaintext all over the place.

Thanks jameshowe, that is good news. I can enable that in my regression tests and it should pass.