What we gain is that people forking the repository can have CI for their forks by enabling Travis there. Might be handy to run CI while working on your branch (and before submitting the PR).
So these users, need to go to travis-ci where they would point to their fork and it would build any given branch of their fork? That might indeed be handy. I guess if we add this file, it would make sense to add a couple of sentences to the README as well. Maybe under the "Build from Source" section. It could mention that using the provided Travis config file, developers can check their work in an CI environment even before creating a pull request. WDYT? Also, if I understand correctly to make the Travis build work we need to first merge HV-1063. |