We are using Jenkins CI/CD integrated with Bitbucket for quite a long time, and we have many actively running pipelines.
With the recent deprecation of Bitbucket App Passwords and the move to API tokens, we are facing issues during integration.
Currently, in our Jenkins credentials, we have stored Bitbucket credentials using username and app password.
These credentials are used in two key places:
-
Job validation – Jenkins uses them to validate and fetch repositories during pipeline setup.
-
Repository cloning – The same credentials are used during Git operations (
git clone,fetch, etc.).
After the deprecation update, Bitbucket now requires API tokens with email for authentication.
However, Jenkins pipelines that use the Git plugin do not support cloning via email + API token, and we are unable to modify all existing Jenkinsfiles or jobs to change this format because of the large number of existing pipelines.
We are looking for a solution or workaround that allows Jenkins to continue authenticating and cloning repositories using the new Bitbucket authentication mechanism — without modifying our existing job definitions or scripts.