Skip to content

Latest commit

 

History

History
40 lines (29 loc) · 1.33 KB

CI.md

File metadata and controls

40 lines (29 loc) · 1.33 KB
Raw

Continuous Integration

For CI are using Travis CI. Every time a PR is merges to master, Travis will create a new release as well. Both a Github release and a docker image will be published.

GitHub Token

In order for Travis CI to perform its duty, a valid GitHub token must be encrypted in the Travis configuration file.

If this token needs to change, here is how to set it up:

  • Log on to GitHub on the account you want Travis CI to impersonate when performing operation on the repository
  • Go to GitHub, in your Personal access tokens configuration
  • Click on Generate new token
  • Check the public_repo scope
  • Click Generate token

We will now encrypt that token with the travis CLI. Make sure it is installed.

travis encrypt GITHUB_AUTH=the_token_copied_from_github

This will encrypt it in a way that only Travis CI can decrypt. Your personal token is then quite safe.

The output should look like this.

  secure: "someBASE64value"

Take the output (the complete YAML key as it appears) and replace, in the .travis.yaml file, this line with the output of the previous command.

env:
- secure: "someBASE64value"