Code clone common issues

When the agent receives a notification to run a build, the first thing it will do is clone the repository. The repository will be cloned using SSH. It means that you need to have a SSH key defined in GitHub for your computer. You can follow this guide from GitHub to do so.

Generating a SSH key is pretty straight forward and there are good chances you are working that way already.

If your key is not setup properly you will get a "Permission denifed (publickey)" error. GitHub has documented the issue thoroughly under this link.

Another common problem is to have your SSH key setup in GitHub but not added to your SSH agent. The error you would get in that case is:

  Cloning into 'fireci'...
  Warning: Permanently added 'github.com,192.30.253.112' (RSA) to the list of known hosts.
  ssh_askpass: exec(/usr/X11R6/bin/ssh-askpass): No such file or directory
  git@github.com: Permission denied (publickey).
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.
To solve this issue just run the following command:
ssh-add -K ~/.ssh/id_rsa


What next?

If this article did not solve your problem not hesitate to contact us at support@fire.ci.