How To Set Up Continuous Integration For A ReactJS App
In doing so, Wercker will take React-Starterify app,
npm install the dependencies, run the tests and build steps specified in the gulp file, push the static assets to Bitbucket, and Aerobatic will automatically update your hosted web app.
- Head over to https://bitbucket.org/repo/import
- In the URL input, paste in the Github repo details:
Either from the command line, or using a tool like SourceTree, go ahead and clone the Bitbucket repo that you just created, onto your local development machine.
$ git clone firstname.lastname@example.org:youraccountname/react-starterify.git
This will be the branch that we deploy our compiled assets to. When Wercker does our gulp build task, it will deploy the compiled assets to this dist branch that will eventually be linked to Aerobatic for hosting.
# Create a new orphan branch (no commit history) named dist git checkout --orphan dist # Unstage all files git rm --cached $(git ls-files) # Grab one file from the master branch so we can make a commit git checkout master README.md # Add and commit that file git add README.md git commit -m "INIT: initial commit on dist branch" # Push to remote dist branch git push origin dist
At this point, we have our react-starterify Bitbucket repository with a master branch and a dist branch. The master branch contains our source code and our dist branch has only a README.md file for now.
We previously used Wercker to build a Hugo static blog, and it was such an easy experience, we're going to use it again for this tutorial.
You'll need to create a Wercker account and connect with Bitbucket. Rather than spell out all the details here, head on over to Wercker and get started there. They have a really nice on-boarding flow:
Wercker uses a
.yml file that outlines the steps in your build process. Below is our
wercker.yml file that we will store in the root of our react-starterify repository.
box: node build: steps: - npm-install - hgen/gulp: tasks: build deploy: steps: - script: name: install git code: | apt-get update apt-get -y install git # Add SSH-Key to - leipert/add-ssh-key-gh-bb: keyname: DEPLOY_SSH # Add bitbucket to known hosts, so they won't ask us whether we trust bitbucket - add-to-known_hosts: hostname: bitbucket.org fingerprint: 97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40 - leipert/git-push: host: bitbucket.org repo: dundonian/react-starterify branch: dist basedir: dist
You'll update the
repo field to match the name of the repo you created in Bitbucket. You may have noticed that the
keyname field has an environment variable value called
In Wercker, create a new SSH Key pair. Copy the public key in Wercker and then add that to your Bitbucket account SSH Keys.
Using the SSH key that we just created, create a new environment variable in Wercker and name it
The final step in Wercker is to create a deploy target.
With Wercker set up to run our gulp tests and build, we can now git push to the master branch and Wercker will deploy our successfully compiled assets to the dist branch.
The demo app is live on Aerobatic at http://react-starterify.aerobaticapp.com/.
Often, with Single Page Apps, our front-end is calling APIs. The Aerobatic API proxy makes many of those operations easier and more efficient for developers.