deploy.sh

#!/bin/bash

set -e # exit with nonzero exit code if anything fails

# install ssh keys
openssl aes-256-cbc -K $encrypted_1df6839761c3_key -iv $encrypted_1df6839761c3_iv -in .travisdeploykey.enc -out .travisdeploykey -d
openssl aes-256-cbc -K $encrypted_2aaf6d71beae_key -iv $encrypted_2aaf6d71beae_iv -in travis-deploy-key.enc -out travis-deploy-key -d

chmod go-rwx .travisdeploykey
chmod go-rwx travis-deploy-key

eval `ssh-agent -s`
ssh-add .travisdeploykey

# clone the current gh-pages branch into the repo folder
git clone -b gh-pages --single-branch git@github.com:Team846/repo.git repo

export NATIVE_TARGET="ARM32"
sbt publish

# go to the out directory
cd repo

# inside this git repo we'll pretend to be a new user
git config --global user.name "Travis CI"
git config --global user.email "robot@lynbrookrobotics.com"

# The first and only commit to this new Git repo contains all the
# files present with the commit message "Deploy to GitHub Pages".
git add .
git commit -m "(potassium): automated deploy to GitHub Pages"

# Force push from the current repo's master branch to the remote
# repo's gh-pages branch. (All previous history on the gh-pages branch
# will be lost, since we are overwriting it.) We redirect any output to
# /dev/null to hide any sensitive credential data that might otherwise be exposed.
git push --force --quiet "git@github.com:Team846/repo.git" gh-pages:gh-pages > /dev/null 2>&1

cd ..

ssh-add -D
ssh-add travis-deploy-key

sbt ';project docs; publishMicrosite'