Nowaday, all the code should be tested before shipped. But we are all human being, we make mistakes. Sometime you are thinking just one line of code, not a big deal, just push it. Unfortunately, that line of code cause errors. So, we need something to automate test our codes after we pushed it to verify our code pass all the test case or not. That’s why CI introduced.

And for CI, in my option, there are two kinds right now, one is Jenkins with docker(more manual) and one is Codeship/travis-ci(more automated).

1) Jenkins with docker

If the project is big and need more security, Jenkins and docker is the choose. Since it’s all configured by yourself. It did not require you to grant all github permissions. But that requires a lot of configuration to make Jenkins and docker work properly. And you have to troubleshoot all the issue by yourself. Normally, it need a release engineer in the team to deal with all those configuration.

But if you are interesting about Jenkins with docker, here’s a great post.

2) Codeship/Travis-ci

So, if your project is small/open source, Codeship/Travis-ci is the way to go. Because it’s easy to setup and it will work flawless as the project grow.

And if your project is open-source, travis-ci is a great tool. Otherwise it will charge 129/mo. So that’s why Codeship is great for small start-up/personal side project, it’s free(100 builds/mo), and it integrate with Heroku and AWS. What you need to do is try to connect with github, and find your Heroku API key. Then everytime when you push to github master, it will run all the test case for you and if all test case passed, it will deploy to heroku. No more configure headache.

Happy CI testing!