Run tests with Travis CI #99
Conversation
|
@dcreager if this passes, should it go into the C-template for all our public C libraries? |
rouge8
force-pushed
the
feature/travis-ci
branch
2 times, most recently
from
db6fb5d
to
efb050d
Compare
|
I am not in favor of putting this in c-template. |
|
It would make it easier to include this with all of our libraries, though our internal projects would immediately remove these edits since Travis wouldn't be able to see our private repos. (Yes there's a way to make it but I'm not ready to open that can of worms yet.) |
Travis is also not free for private repos. For private repos, we can use Jenkins + Docker images like our other projects. I still prefer Travis for public repos because it makes it easier for any potential contributors. |
dcreager
force-pushed
the
feature/travis-ci
branch
2 times, most recently
from
1e47b62
to
f2b28fd
Compare
Use [Travis CI](https://travis-ci.org) to build pull requests and branches. Travis only provides 64-bit build VMs, so we use some multilib magic to test both 32- and 64-bit builds.
dcreager
force-pushed
the
feature/travis-ci
branch
from
f2b28fd
to
db40b31
Compare
|
I've pushed up a new patch that tests both 32-bit and 64-bit builds, using both clang and gcc. It'd be nice to also be able to automatically test on OS X, but Travis is currently at capacity with their OS X infrastructure. |
| @@ -1,5 +1,7 @@ | |||
| # libcork | |||
|
|
|||
| [](https://travis-ci.org/redjack/libcork) | |||
There was a problem hiding this comment.
When we merge this to master, we should update the build status link.
|
👍 |
Travis also [supports](http://docs.travis-ci.com/user/multi-os/) building on OS X.
|
Ah well, it was worth a shot. The latest patch updates the travis scripts to work on OS X (tested on my MBP), but Travis isn't showing the OS X builds in the matrix. If at any point we can convince Travis to turn on OS X builds for libcork, then our build scripts will be ready for it. |
Use Travis CI to build pull requests and branches.