Authentication¶
BLCI requires you to already have authentication credentials to:
- Github
- Travis CI
- SSH keys setup for Github (TODO: Won’t be necessary in the future)
- A Github OAuth token
SSH Keys¶
You must have setup SSH keys to allow password-less authentication to your Github
repos already. If you do not, follow the steps outlined
here
and copy and add your id_rsa.pub public key to your Github account at
https://github.com/settings/keys.
Lastly, In order to allow BLCI to create an autonomously managed Github and Travis CI repos you will need an authentication token.
OAuth authentication token¶
Follow the steps outlined
here.
Copy and paste the token into a file in the root of your project. The default name that BLCI
expects is .credentials, but you can set the
credentials
setting in the blci.yml configuration to adapt the default behavior.
Your token file will never be tracked by Git or BLCI.
It must remain local and untracked!
Permission level required for OAuth token¶
Your token must select the following scopes:
- repo
- read:org
- admin:repo_hook
- user:email
- delete_repo