I've configured Travis CI builds for the 'librambutan' repository:
This means that code pushes (or merge requests) to the librambutan github repository will result in the code being checked out and some basic builds being run remotely. Tests aren't actually getting run on a microcontroller, but this is a great way to check for build errors as quickly as possible, especially for merge requests.
What exactly gets built is controlled by the
.travis.yml file. To start things off, the same program (
examples/test-session.cpp) gets built for 3 different boards (maple_mini, maple_native, and st_stm3220g_eval). Only
maple_mini builds successfully with this program right now; work to do!
In the future would be possible to integrate linting (aka, checking code style), static checking, etc.