Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Permission denied (publickey) when running git from PowerShell task in a scheduled deployment

I have a deployment project setup to deploy some code to a web server. When the deployment completes, I run a PowerShell script task that does the following:

* Clones the repository onto the build server (we're running Bitbucket server internally).

* Tags the commit.

* Pushes the tags.

If I run this task by running the deployment project manually everything works. However, if I run the task on a schedule I get:

"Permission denied (public key)" on the clone step.

The private key is on the build server and the public key is setup in Bitbucket. What could I be missing here? Is there a difference between how Bamboo runs a deployment on a schedule versus being kicked off manually?


1 answer

Right as I posted this I realized the problem. I have a remote agent setup that I forgot about. The agent without the private key setup is always running the scheduled deployments for some reason and the local agents are always running the manual deployment.

All I have to do is either add a required capability to the environment, setup a private key on the other agent or setup the dedicated agents on the environment. 

Maybe this will help someone who runs into a similar issue.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events