nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Git and Bamboo Remote Agent?

Timothy Harris

Hi,

I have Bamboo running on a windows server as SYSTEM user.

I have one remote agent, which is also ran as SYSTEM user.

The git clone command fails. Do I have to set up ssh keys on each remote agent? If so doesn't that mean I have to run Bamboo and Bamboo remote agents as a specific user and not a SYSTEM user?

Any advice on the best way to set up remote agents and access to repositories in the most generic way would be appreciated. The Bamboo server will be a centrally maintained instance where we want to easily add remote agents as the number of teams increase.

Accepted answers

All comments

Mike Friedrich

I always had problems getting ssh running as SYSTEM.

It is much easier if you configure the agent service to run as a specific "auto-build" user.
Then you can login yourself and prepare the environment (keys, knownhosts etc.).
Also you then can configure permissions on Bamboo (or Stash if you use that) for that user if thats also needed.

I am running Bamboo server on linux now but also tested it on Windows some tme ago. For Windows i think i also used the same user as the service account.

And yes, you have to configure ssh keys on the server and on each agent. Especially if you use submodules. If you dont use them you might get away with just configuring shared credentials in Bamboo.

Daniel Wester

You only have to configure the ssh keys on the server and the agent if you're shelling out to command line as part of your build (and even then you can pass in the ssh tunnel to use so you don't need to do that).

If you're using the Checkout from Source task you just have to upload the ssh key into the task's configuration.

What's the error you're getting? It might be more of a system issue.

Mike Friedrich

That is incorrect if Use Submodules option is enabled.

Daniel Wester

That might be true (and I don't know about submodules usage in Bamboo since I haven't had to use them in a while) but he didn't ask about submodules but rather "to set up remote agents and access to repositories in the most generic way ". But if you want to use submodules with ssh keys - there's a feature at https://jira.atlassian.com/browse/BAM-11369 it has how Atlassian does it (more specifically https://jira.atlassian.com/browse/BAM-11369?focusedCommentId=552009&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-552009 )

Mike Friedrich

I think thats a genreic problem of the git submodule command. Bamboo still uses the configured git.exe command executable for the agent for any submodule handling (instead of a java implementation). As long as the "git submodule" shell command is used, it will have the problem i mentioned. This command does not use Bamboo shared credentials and i dont know a way how Bamboo could pass these credentials unless they do something like copying the private key to $HOME/.ssh/id_rsa (or in Windows the users profile home directory) before starting the first git command.

Timothy Harris

I am wondering if the real issue is this:

error: cannot spawn C:\WINDOWS\system32\config\systemprofile\AppData\Local\Temp\bamboo-ssh.41538fd5.bat: No such file or directory, fatal: unable to fork

If the agent, which is running as SYSTEM user does not have access to system32\config\systemprofile\AppData\Local\Temp to create the .bat file?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server

bamboo

remote-agent