I've been running a Jenkins build bot for cabal for quite a while:

It's not as good as it could be, because the Cabal test suite isn't in the best shape. In particular the InternalLibrary tests are failing at the moment and I think it's because the tests actually modify the shared package DB (i.e. the user DB)!

If you could figure out why they're failing and/or make the test suite more robust (i.e. it should create a new empty package DB every time) that would be great.

On Sat, Aug 31, 2013 at 9:43 AM, Paolo Giarrusso <p.giarrusso@gmail.com> wrote:

Hi all,
I'm at Zurihac and I'm experimenting with setting up Travis
integration for cabal (I've never used Travis before); Duncan Coutts
told me to coordinate with you, since you've been also thinking about
this.

I'm also trying out using Ceh (presented at this ZuriHac itself,
presentation visible by downloading
https://github.com/errge/ceh/blob/master/doc/fpafternoon-zurich-20130829/final/)
to get an updated Haskell version (rather than the default Haskell
platform from last year); if this works, we can maybe try out testing
cabal on different versions.

I'll keep playing with this for a while.
Comments and suggestions are welcome!

Cheers,
Paolo

--
Paolo G. Giarrusso - Ph.D. Student, Philipps-University Marburg
http://www.informatik.uni-marburg.de/~pgiarrusso/