5 Steps to build NodeJS using Travis CI
April 13, 2016
Or in simple terms, when you push a commit to the master branch of your project hosted at GitHub, Travis CI will run tests and build the latest commit of your master branch.
It’s that simple. You push a commit → Travis CI run tests and build. Automatically.
Go to Travis CI. Sign in using your GitHub account. You will be prompted to authorise Travis CI to your GitHub account. Approved that.
When you see something like this:
Voila. You have created a Travis CI account.
Next thing you are going to do is to click the
(+) button beside the “My Repositories” on the left.
You will then see a list of projects on your GitHub.
If the list of repositories is empty, click “Sync account” to fetch all your repositories.
Turn on one of your project for Continuous Integration!
Create a file name
.travis.yml at the root folder of your project.
Copy this into the file.
language: node_js node_js: - 4.2
Commit and Push. That’s simple.
Or if you are lazy, run this:
curl https://gist.githubusercontent.com/tanhauhau/405e39884e80288615a7b51181fd5228/raw/9045c2e219547f0a228da630abff345d8add0c47/.travis.yml > .travis.yml
The version of Node.js I am using is 4.2 at the time of writing this article. To be safe, you can run “node — version” on your command line to determine which version of Node.js you are running.
Make sure that you have all your dependencies persists to the package.json as Travis CI will install all the dependencies from it by calling npm install.
Another thing to take note is that if you wanna run your test script, make sure to include it in the
If you are using bower, add a before_script for .travis.yml
language: node_js node_js: - 4.2 before_script: - npm install -g bower - bower install
Or likewise if you are lazy, copy and paste this to your command line.
curl https://gist.githubusercontent.com/tanhauhau/71998bf221810186f046db94cda10c4e/raw/d1e8aee0981a96c20f94de6db386da048face423/.travis.yml > .travis.yml
One thing to take note for bower is that when there is dependency conflict, bower will ask you to choose which version of the dependency to be installed interactively. In the case for Travis CI, Travis CI will not know which version to install it for you where you will see an error like this:
Therefore, you will have to persists the resolution to bower.json to avoid the build error.
To summarise, you have set up your Travis CI, copied and pasted the
.travis.yml to your project, commited and pushed your project to GitHub, and Travis CI had built and tested your project.
Now, it’s time to add a badge to your GitHub repository!
Simply clicked the badge in Travis CI and choose for Markdown.
Copy and paste the line into your README.md.
Commit and Push.
And now you have a Travis CI badge on your repo!
Thank you for your time reading through this article.
It means a lot to me.
If you like what you have just read,
Tweet about it so I will write more related articles;
If you disagree or you have opinions about this article,
Tweet about it too so I can take your suggestions and improve on it.