-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 2.222.3, git plugin 4.2.2, git client plugin 3.2.1 and pre-release versions from the master branch of the git plugin and git client plugin
-
-
git client plugin 3.6.0
I upgraded my Bitbucket account to use two factor authentication. As part of that upgrade, I needed to switch from using my actual Bitbucket password in the https credentials that clone repositories to use an app password instead.
The change from using my actual Bitbucket password to app password (personal access token in GitHub parlance) was easy for the jobs that use command line git. I changed the credential value from actual password to app password and the job continued to clone and run successfully.
Jobs that use JGit and JGit-apache were previously working correctly with the actual Bitbucket password. With the change from actual Bitbucket password to an app password, they are no longer able to clone from Bitbucket.
Alternatives to avoid the issue include:
- Use CLI git instead of JGit
- Use ssh protocol ( git@bitbucket.org:markewaite/bin.git ) instead of https protocol ( https://markewaite@bitbucket.org/markewaite/bin.git )