Monad-par Jenkins testing

[Ryan Newton]

Following Johan's example I set up Jenkins based continuous integration for monad-par.  After doing a bit of legacy-support hacking just now things are in decent shape from 6.12.3 all the way to 7.4.  (Screenshot attached.)

It seems like it should be nearly push-button to add more packages, as long as the test is the same (cabal install && cabal test) ***, so I would be happy to test other people's packages as well.

Johan, is this the idea with the accounts other people have on http://ci.johantibell.com/, that they can test their own packages?  

(Do you have a pointer for setting up user accounts / password access with Jenkins.  I did some failed googling on that front.)

Cheers,

  -Ryan

*** Actually, to be honest, I'm still observing discrepancies in behavior between "cabal test" and running the tests manually (ghc --make) that I have yet to explain.  Hopefully others are having better luck.

[Johan Tibell]

Hi Ryan,

On Sat, Jan 7, 2012 at 3:29 AM, Ryan Newton <rrne...@gmail.com> wrote:
> Johan, is this the idea with the accounts other people have
> on http://ci.johantibell.com/, that they can test their own packages?

I'm the only one with an account on my server. I do build a few
packages for other people (like HTTP) though.

> (Do you have a pointer for setting up user accounts / password access with
> Jenkins.  I did some failed googling on that front.)

I use the OpenID login. I read some article on securing Jenkins that
told me how to set it up.

-- Johan