We currently use an app password to authenticate from jenkins to bitbucket cloud (we use multi-branch pipelines for branch detection). However we recently saw a deprecation notice for app passwords saying we should move to api-tokens, but I guess that api-tokens can't be used for this case (we keep getting 401 errors when we use an api-token). How should we setup our authentication when we can't use app-passwords anymore?
Community moderators have prevented the ability to post new answers.
I'm assuming you need to connect to the Bitbucket Cloud REST API with Jenkins, correct? Are you achieving this via a webhook on the Bitbucket Cloud side or is it an integration on the Jenkins side?
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.