Hi All , we have several Github repos linked to bamboo and we have a couple of jobs that run in parallel. Recently we are seeing issues where the builds fail to start with the error :
com.atlassian.bamboo.plugins.git.GitCommandException: command [/bin/git ls-remote ssh://somerepo.git] failed with code 128. Working directory was [/bms/webapps/bamboo/current/temp]., stderr: Warning: Permanently added '[127.0.0.1]:45737' (RSA) to the list of known hosts. BAMBOO-SSH-PROXY: [User session has timed out idling after 120000 ms.] fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
It's not really a permission error because the same job on re-triggering works. I just want to understand where is the BAMBOO-SSH-PROXY configured and how to make sure that a lot of builds do not fail with the same error in future.
The issue is with GitHub rate limits. Even though the credentials and proxy work, GitHub was rate limiting my user so that I can't make more than certain number of requests per minute and hence was hitting this issue. It would have been a bit better if the error was more specific rather than the generic
fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
removed the rate limiting on GitHub server to fix this issue.