Skip to content

Instantly share code, notes, and snippets.

@vidavidorra
vidavidorra / Travis-Ci_publish_to_GitHub.md
Last active February 22, 2016 16:54
Example of Travis-CI to publish to GitHub

Travis-CI publish to GitHub

Generating a personal access token for GitHub

  1. In GitHub, go to settings and Personal access tokens;
  2. Click Generate a new token and fill in the description;
  3. As scope select repo;
  4. Copy the generated token.

Adding the secure variable to Travis-CI

Method 1: Using the Repository Settings

Similar to the Travis-CI documentation

Installing and setting up CooCox CoIDE

  1. Download CoIDE (link)
  2. Install CoIDE
  3. Download the GCC ARM Embedded compiler (link)
  4. Install the GCC ARM Embedded compiler and select Launch gccvar.bat on finish
  5. Configure the compiler
  • Open CoIDE
  • Project > Select Toolchain Path
  • Browse and find the installed GCC ARM Embedded compiler (C:\Program Files (x86)\GNU Tools ARM Embedded\5.3 2016q1\bin)
  • Hit the OK button
@vidavidorra
vidavidorra / auto-deploy_documentation.md
Last active February 19, 2023 17:37
Auto-deploying Doxygen documentation to gh-pages with Travis CI

Auto-deploying Doxygen documentation to gh-pages with Travis CI

This explains how to setup for GitHub projects which automatically generates Doxygen code documentation and publishes the documentation to the gh-pages branch using Travis CI. This way only the source files need to be pushed to GitHub and the gh-pages branch is automatically updated with the generated Doxygen documentation.

Sign up for Travis CI and add your project

Get an account at Travis CI. Turn on Travis for your repository in question, using the Travis control panel.

Create a clean gh-pages branch

To create a clean gh-pages branch, with no commit history, from the master branch enter the code below in the Git Shell. This will create a gh-pages branch with one file, the README.md in it. It doesn't really matter what file is uploaded in it since it will be overwritten when the automatically generated documentation is published to th