Bitbucket Cloud: "You are currently connecting with your team account. This is no longer supported, so please connect using your user account."

[Adam Parkin]

We recently started seeing this warning in our CI server.

Currently we have an SSH key on our Bitbucket team account, and this key is what our CI server (Jenkins) uses to authenticate with Bitbucket (on a successful build Jenkins pushes a commit on a particular branch to Bitbucket).

We don't want to create a dedicated user for our CI server, so how can we resolve this warning without doing so?

[Kevin Shu]

As suggested by Atlassian Support, I created a feature request on the public issue tracker to ask for correctly supported service accounts

https://bitbucket.org/site/master/issues/15600/ability-to-use-service-account-on

[Adam Parkin]

Anyone?  This is now proving to be extra annoying as we'd like to start setting branch restrictions so that only our CI server can commit to our mainline release branch, but to do so we'd have to add another full Bitbucket user and we're currently at our usage cap (so adding one more would mean a significant increase in price for relatively little benefit).