I am using SSH Keys set on the team account to automate some operations related to my repositories (checkout, build, test, merge and push)
The server is emitting the following warnings :
remote: Warning! remote: You are currently connecting with your team account. remote: This is no longer supported, so please connect using your user account.
How am I supposed to update my process? The recommended way of providing automation seems to be using SSH Access keys, but these only allow Read-Only access, no write access.
Hi Kevin! You can not manage a repository using a team account anymore. Team administration changed and you can no longer use an email address to access a team or manage repositories using a team account. Now, team members use their individual Bitbucket accounts to access the team and commit changes. This was announced at Team account changes. You'll need to automate those operations using your individual Bitbucket account, given that your Bitbucket account has access to those repos.
Hope this helps!
Thanks Ana for your reply. I did see the page you mention but I was hoping there would be another way.
I also saw that Bitbucket Server allows SSH Keys with read-write access.
Is this something that is planned to be implemented in Bitbucket Cloud?
@Ana Retamal Ortiz : What are we expected to do on our Continuous Integration solutions? It is quite irrational to use a specific software engineer's bitbucket account to have the CI server push versioning changes to Bitbucket. We have to register a standalone brand new Atlassian account for our bots?
Thanks in advance.
I whole-heartedly agree with @Adam Rocska. What your suggesting we do, using an individual's SSH key for what's effectively a service account, is atrociously bad practice.
If the only way to do it is to create a new dedicated account then I guess that's what we'll have to do, but that's really chumpy. Why the change?
My use case is Bitbucket Pipelines. I have three custom pipelines corresponding to the three numbers in semver (major, minor, patch) which need to push a tag and changes to master and develop. The problem is that git in Pipelines can't push to the remote, so I generated a team-level SSH key and set that as the SSH key in Pipelines. I'd be happy to do away with the team-level SSH if Pipelines can be enhanced to allow pushing back to remote.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot