Need new continuous integration testing (e.g. Travis CI)

[pnkfelix]

We use to use CDash for continuous integraton testing (via a server that was sitting in the basement of where I lived years ago).

That's no longer a viable option, for many reasons.

But luckily we live in an age where there's lot of new options for continuous integration testing.

[WillClinger]

Every since Larceny v0.99 came out, Travis CI has been trying and failing to build Larceny every time we push new changes to GitHub.

I don't know why. I suspect I looked into using Travis CI for Larceny, and got far enough along to realize it wasn't really feasible, but failed to undo whatever I had done during the attempt. It's also possible that Felix or someone else did that. At any rate, we really ought to turn off the routine Travis CI failures.

We do have nightly builds running on Linux and MacOS X machines, and lack of a suitable always-on desktop machine is the only reason we don't have nightly builds for ARMv7 Linux and Windows machines. I'm reasonably happy with the reporting on our nightly builds and would prefer to improve our current infrastructure instead of handing it over to Travis CI.

[pnkfelix]

I'll look into turning off the Travis stuff

[pnkfelix]

(Hmm I somehow deleted my last comment... reconstructing...

[pnkfelix]

Okay I disabled the Travis service (which I believe I turned on back when I thought I had time to set it up). I didn't delete the service but I imagine any of the larcenists with admin rights could so if necessary.

steps

navigate to "integrations and services", via "settings" tab on top

navigate to "manage Travis", via "Travis CI" link

uncheck the "Active" box

[pnkfelix]

(I do think we could use Travis; it's a matter of figuring out how to get it to set up an appropriately configured VM, namely with all the build tools including a copy of Larceny installed for bootstrapping.)