Two version of GIT install (in C & D drive) by accident this lead to fatal: Authentication failed ..

Question

The previous GIT was installed in D drive by someone, just recently, one of our big team member try to add capabilities into one agent. At the beginning did not see this GIT already listed in the agent, also checked it in Control Panel, still not seen since it is in D drive. Therefore by accident, a old version of GIT installed again in C drive, later I saw it is installed in D drive therefore uninstall the GIT on C drive. However, because of this our bamboo plan is always complaining this below errors and no agent to run, the bamboo build failed to launch... Is this because of the local agent removed by accident as below: 18:17, 4 Apr 2024 system.builder.command.local agent It is sort of disaster to us. Is anyone having such experience and have a solution to solve this issue? It looks like something to do with git credential-store. keep getting Authentication failed error (com.atlassian.bamboo.plugins.git.GitCommandException : command [D:\BuildUtilities\GIT\bin\git.exe -c credential.helper= -c 'credential.helper=store --file=D:/Program Files/BAMBOO~3/temp/GITCRE~1.TMP' ls-remote http://xxxxx@xxxxxx2:7990/stash/scm/narta/pnponline-library.git failed with code 128. Working directory was [D:\Program Files\Bamboo-8-1-3 emp]., stderr: usage: git credential-store [] --file fetch and store credentials in usage: git credential-store [] --file fetch and store credentials in fatal: Authentication failed for 'http://xxxxxx2:7990/stash/scm/narta/pnponline-library.git') Whenever to test connection on Bamboo plan, always show up this error as below: usage: git credential-store [] --[no-]file fetch and store credentials in usage: git credential-store [] --[no-]file fetch and store credentials in fatal: Authentication failed for 'http://xxxxxx2:7990/stash/scm/narta/pnponline-library.git/' Thanks for your attentions and any thoughts and clues shall be greatly appreciated! Will

Shashank Kumar · Accepted Answer

Hello William,

Welcome to Atlassian community

I assume all of the above problems are on your local agents and not Bamboo.

18:17, 4 Apr 2024   system.builder.command.local agent

The above seems to a manually defined a capability which you seems to have removed it from Bamboo GUI, you can add this capability again if it's required by your Jobs to run

Regarding problem with your GIT Installation, at this point I assume you have GIT installed in your D Drive, I am not sure if Bamboo local agent is able to detect the GIT capability correctly, but you can restart your Bamboo server to make sure during restart the local agent detects the correct GIT capability, please make the GIT executable are present only at one location.

Post restart verify the capabilities page of the agent and make sure GIT is listed there properly. Bamboo will auto detect this, If not add the correct GIT capability.

Also looking at the error I think the problem is with the space in the path of temp directory defined at D: \Program Files\Bamboo-8-1-3	emp

Can you try the solution at https://confluence.atlassian.com/bamkb/bamboo-on-windows-throws-an-authentication-error-when-adding-a-linked-repository-1047542448.html and let me know the results.

Regards,

Shashank Kumar