Building Eiffel projects with TravisCI

Eiffel CI Tutorial: Getting Started with TravisCI

We know that we need to test our applications thoroughly to catch problems before they affect our users. Eiffel Developers has the advantages of Design by Contract, but we also need to double check our code. Forgetting to test can result in complications, endless debugging sessions, money, etc, but remembering to run test cases before each commit, pull-request or merge can be can be difficult if you have to do it manually.

Continuous Integration

Continuous Integration, often abbreviated to just CI, is the process of automatically building and running tests whenever a change is committed. In this tutorial, we will cover Travis.CI

Note:
You need to sign up for a GitHub account if you do not already have one.

Getting-Started with Travis CI

What is Travis CI?

It’s a Continuous Integration service that is free for open-source projects and has a monthly fee for closed-source projects based on how many simultaneous builds you want to run.

What does it do?

Travis sets up hooks with GitHub to automatically run tests at specified times. By default, these are set up to run after a pull request is created or when the code is pushed up to GitHub.

In this tutorial, we will use a public GitHub repo and the free version of Travis to set up tests that run every time you try to merge new changes into the repository.

Once you’re signed in,Travis synchronized your repositories from GitHub, go to your profile page and enable Travis CI builds for your fork of the EiffelCI repository. Take a look at .travis.yml, the file which tells Travis CI what to do: