.travis.yml

language: ruby
rvm:
  - 2.3.7
before_script:
  - gem install bundler
script: bundle exec jekyll build
after_success:
  - ./push.sh
env:
  global:
    - secure: # SOMETHING SECURE
              # USE travis encrypt GH_TOKEN=[GitHub Token]

README.md

Orgirianlly from https://ayastreb.me/deploy-jekyll-to-github-pages-with-travis-ci/

Deploy Jekyll to GitHub Pages with Travis CI If you want to use GitHub Pages with custom Jekyll plugins (e.g. anything other than officially supported plugins) — you need to generate the site content and push it to the repository manually. If you want to automate this step and deploy your site every time you push changes to Jekyll, Travis CI might help you. Travis CI is a continuous integration tool which allows you to setup build process for your GitHub repo. It is free for public repos. Every time you push changes to the repository, Travis CI will setup a virtual machine and run the build script you provide it.

Travis Configuration Since Jekyll runs on Ruby, we need to tell Travis to setup a VM with Ruby environment. We need to create .travis.yml file in the root of the repository for that.

language: ruby
# only run CI-builds on master branch
branches:
  only:
  - master
rvm:
- 2.2.3
# set execution permission on our build script
before_script:
 - chmod +x ./script/cibuild
# path to our build script. 
# Travis will run `bundle install` by default before running our script
script: ./script/cibuild
exclude: [vendor]
sudo: false

Build Script To deploy our Jekyll site we need to push generated static content to gh-pages branch of our repository. To achieve this we need to do following:

clone our repo at gh-pages branch with write permissions to _site directory build Jekyll site to _site directory commit and push all changes in _site directory to gh-pages branch We need to create personal access token and set it in Travis build “Environment Variables” settings to be able to clone the repo with write permissions.

Then we need to add following Bash script to script/cibuild in our repository:

#!/bin/bash

# skip if build is triggered by pull request
if [ $TRAVIS_PULL_REQUEST == "true" ]; then
  echo "this is PR, exiting"
  exit 0
fi

# enable error reporting to the console
set -e

# cleanup "_site"
rm -rf _site
mkdir _site

# clone remote repo to "_site"
git clone https://${GH_TOKEN}@github.com/ayastreb/11route.git --branch gh-pages _site

# build with Jekyll into "_site"
bundle exec jekyll build

# push
cd _site
git config user.email "anatoliy.yastreb@gmail.com"
git config user.name "Anatoliy Yastreb"
git add --all
git commit -a -m "Travis #$TRAVIS_BUILD_NUMBER"
git push --force origin gh-pages

After this is done, Travis will run the build script after every push to master branch and deploy the generated static content to gh-pages branch automatically!

Written on May 29, 2017

push.sh

#!/usr/bin/env bash
# Push HTML files to gh-pages automatically.

# skip if build is triggered by pull request
if [ $TRAVIS_PULL_REQUEST == "true" ]; then
  echo "this is PR, exiting"
  exit 0
fi


# Fill this out with the correct org/repo
ORG=github
REPO=github
# This probably should match an email for one of your users.
EMAIL=example@example.com

set -e

# cleanup "_site"
rm -rf _site
mkdir _site


# clone remote repo to "_site"
git clone https://${GH_TOKEN}@github.com/$ORG/$REPO.git --branch gh-pages _site

# build with Jekyll into "_site"
bundle exec jekyll build

# push
cd _site
git config user.name "Travis Build"
git config user.email "$EMAIL"
git add --all
git commit -a -m "Travis #$TRAVIS_BUILD_NUMBER"
git push --force origin gh-pages