Enable continuous integration

[mathiasbynens]

With this change, every commit pushed to master and every pull request received triggers a build. If anything breaks, e.g. if the MD5 hashes for generated ROMs are incorrect, it automatically reports an error straight in the GitHub pull request UI.

Example build log: https://travis-ci.org/PoCs/pokered/builds/151586998

For this to work, you’d have to enable Travis for this repository: https://docs.travis-ci.com/user/getting-started/#To-get-started-with-Travis-CI%3A

[kanzure]

What's check_status for, here?

[mathiasbynens]

It would detect edge cases where running make alters a Git-tracked file. That could happen if someone tries to sneak in a commit that, when running make afterwards, changes the generated 2bpp or pic files, for example.

Consider my patch in #92: at the moment, the only way to verify that it doesn’t mess anything up is by merging it locally, running make, and confirming there are no uncommitted changes. But with this change, that check would happen automatically as soon as anyone submits a PR.

[mathiasbynens]

Can someone review this please?

[dannye]

I'm not speaking for everybody, but I don't think this is in our interest. Our makefile already verifies the output rom.
The other features of Travis - automatically posting to the Github PR, detect when make alters tracked files - just don't seem very necessary.

[bgourlie]

Considering how low-lift adding CI to this project would be, I don't understand how anyone could argue against it.

[kanzure]

ACK, this looks reasonable to me. I like the idea of introducing continuous integration to the project and its users, who may be unfamiliar with the benefits of regular testing and builds. Let's do this.

[Sanqui]

Is anybody still opposed to this? I've updated (Sanqui@d7bd7f4) the Travis script and I'm ready to set it up.

[Sanqui]

Improved and accepted in #148, thank you!