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?
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.
We’re preparing for Bamboo 8.0, which will be our first Data Center release. To make sure our app vendors and customers with written in-house apps are prepared, we’re launching Bamboo 8.0 Early Acces...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events