Bitbucket App Password replacement for Jenkins

[Frank Ulbricht]

I understand that Bitbucket discontinues the App Passwords. We are using App Passwords for cloning repos in Jenkins jobs.

Until now, I have tested API Tokens, Scoped API Tokens, Repo Access Tokens and nothing is working as expected. What is the suggested way to setup credentials to a Git repo in Jenkins now?

We do not only need to clone the repo but sometimes also push changes to it. I do not want to include any kind of secret token in my pom.xml. How is that working now?

[Syahrul]

Hey @Frank Ulbricht 

Welcome to the community!

An API token works similarly to an app password, but with limited permissions. If you'd prefer not to use an API token, you might consider an alternative connection method like SSH. This way, you won't need to worry about managing secrets, since you'll be using an SSH connection instead of username and token authentication.

I hope this helps.

Regards,
Syahrul

[Qualitype Tool Access]

Hi Syahul,

thank you for your response.

By saying "limited permissions", does it work in a plain git command line or not. As far as I tried, it does not. Would be great to know this as a fact.

An if it shall work, how does the URL must look like?

Thank you!

[Qualitype Tool Access]

Update:

I just tried it again and it works. I use an API token with scopes in the git command line. Also, the Jenkins jobs I configured on Friday just did some self-healing over the weekend. They work too, without any changes. There must have been some other problem on Friday, out of my responsibility.

Whatever happend, now it works.

Thank you!