Repurpose amor-main as a superbuild (YCM-enabled) repo

[PeterBowman]

Examples:

• https://github.com/roboticslab-uc3m/asibot-main
• https://github.com/roboticslab-uc3m/teo-main

[PeterBowman]

The main handicap is the private amor-api repo, which requires Travis to work with deploy keys. Here is the full procedure:

• Generate a SSH public/private key pair: ssh-keygen -t rsa -b 4096 -C "your_email@example.com".
• Paste the public key into GitHub repository settings > deploy keys (private repo you want to access to, e.g. amor-api).
• Install the Travis CLI utility: gem install travis (you'll need Ruby).
• Change directory, move to the repo you want to connect via Travis with the private one (e.g. amor-main).
• Log in with your GitHub credentials: travis login --pro.
• Encrypt private SSH key: travis encrypt-file /path/to/id_rsa -r roboticslab-uc3m/amor-main. This will generate a id_rsa.enc file in your current working directory.
• Deploy encrypted key into Travis repository settings: travis env set DEPLOY_KEY_AMOR_API `base64 -i ./id_rsa.enc | tr -d '\n'` --private -r roboticslab-uc3m/amor-main.
• Go to Travis repository settings (https://travis-ci.org/roboticslab-uc3m/amor-main/settings) and check that you have new encrypted environment variables (DEPLOY_KEY_AMOR_API, encrypted_xxxxxxxxxxxx_key and encrypted_xxxxxxxxxxxx_iv).
• In your .travis.yml, paste this into the before_install section:

  - mkdir -p ~/.ssh
  - echo $DEPLOY_KEY_AMOR_API | base64 --decode | openssl aes-256-cbc -K $encrypted_xxxxxxxxxxxx_key -iv $encrypted_xxxxxxxxxxxx_iv -out ~/.ssh/id_rsa -d
  - chmod 600 ~/.ssh/id_rsa
  - echo "Host *" >> ~/.ssh/config
  - echo "    StrictHostKeyChecking no" >> ~/.ssh/config
  - echo "    CheckHostIP no" >> ~/.ssh/config
  - echo "    PasswordAuthentication no" >> ~/.ssh/config
  - echo "    UserKnownHostsFile=/dev/null" >> ~/.ssh/config

  (rename DEPLOY_KEY_AMOR_API, encrypted_xxxxxxxxxxxx_key and encrypted_xxxxxxxxxxxx_iv according to the keys generated and uploaded into your Travis repository settings)

• Remember to use the git@github.com: base address when cloning private repos.
  • In YCM-enabled repos (e.g. amor-main): cmake .. -DYCM_GIT_GITHUB_BASE_ADDRESS="git@github.com:".
  • As a standalone clone operation: git clone git@github.com:roboticslab-uc3m/amor-api.

Useful links:

• https://gist.github.com/zhujunsan/a0becf82ade50ed06115
• https://gist.github.com/lukewpatterson/4242707#gistcomment-2382443
• http://anil.recoil.org/2013/10/06/travis-secure-ssh-integration.html
• https://linuxcommando.blogspot.com.es/2008/10/how-to-disable-ssh-host-key-checking.html
• https://askubuntu.com/q/87449
• https://gist.github.com/douglasduteil/5525750
• https://docs.travis-ci.com/user/private-dependencies/

[PeterBowman]

Done at https://github.com/roboticslab-uc3m/amor-main/commit/5a3ba35040c67d8b9740b08ac7b107725c43679e.

[PeterBowman]

It's hard to believe, but... it really looks like repos which configure deploy keys in their Travis settings lack CMake color output in CI builds. I want my colors back!