[racket-dev] Using Travis CI for Racket

From: Greg Hendershott (greghendershott at gmail.com)
Date: Wed Jul 3 16:13:18 EDT 2013

This is cool. One way I've seen Travis CI help especially is with pull
requests via GitHub. The integration is really nice. If someone's pull
request breaks the build or tests, that is highlighted right there in
the pull request "discussion thread" on GitHub. As a result, a
contributor gets automatic feedback to fix it.

BTW, I've wanted to use Travis CI for projects written _in_ Racket.
What you did nudged me to try this, and I took some inspiration from
https://github.com/RayRacine/rackos and came up with

On Tue, Jul 2, 2013 at 7:04 PM, Sam Tobin-Hochstadt <samth at ccs.neu.edu> wrote:
> I've just committed support for building Racket automatically on the
> Travis continuous integration service.  See
> https://travis-ci.org/samth/racket/ for the current build state.  This
> doesn't track the actual `plt/racket` repository yet [1], but once it
> does, it will do the following:
>  - Build the core of Racket on every push (comparable to the "Minimal
> Racket" snapshot)
>  - Run the tests relevant to that core.
> That's it -- this is a free service, and you can't take too much of
> their time.  This isn't a replacement for DrDr, which runs _very_
> comprehensive tests. But it provides very fast turnaround, multiple
> compilers, and eventually OS X and Windows builds. Initially, no one
> will get email -- let me know if you want to be emailed about build
> results.
> Currently, it runs tests for the following:
>  - everything in `tests/racket/`
>  - `json`
>  - `xml`
> Unfortunately, that `pkg` tests seem to break right now.
> Let me know if there's something else that should be run to test that
> "Minimal Racket" is working.
> Sam
> [1] That should happen once Eli is back to flip the relevant
> configuration switch.
> _________________________
>   Racket Developers list:
>   http://lists.racket-lang.org/dev

Posted on the dev mailing list.