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?
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).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs