On 7/12/14, Joachim Breitner wrote:

Hi,

I just added a .travis.yml file to GHC master. This means that every push will be validated automatic and for free by travis; you can check the build status at https://travis-ci.org/ghc/ghc/builds

It is not a full validation. In particular, * it skips DPH * it does not build dynamic libraries and no dynamic executables * does not build haddock or generate documentation * only runs fast tests, and no performance tests

This way we stay under the 50 minuite limit.

Failures are reported to me, and I’ll manually report relevant breakage to you. It is also configured to mail to ghc-builds@haskell.org, but I don’t see these messages there. Maybe some mailing list admin needs to whitelist mails from Travis CI ?

I’ve also added a link to it from http://ghc.haskell.org/trac/ghc/, including a nice icon showing the current build status.

Heh, cool, just added that thingy to the GitHub front page. Thanks for this awesome feature, Joachim! Gabor

If you have that .travis.yml file in your branch, travis will also test these.

My unofficial ghc-complete repository is therefore obsolete, I stopped updating it.

Greetings, Joachim

-- Joachim “nomeata” Breitner mail@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org

This is all fantastic, thank you Joachim. But how would a new GHC dev find out this information? Could it please be documented on the wiki? Perhaps a page called Continuous integration and buildbots to cover both Travis and the buildbots? I'll call it the "CI page". How would one find the CI page? I looked at Working on GHC: https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions An item in the first bulleted list, pointing to the CI page Status reports: https://ghc.haskell.org/trac/ghc/wiki/Status Has a section called "Nightly builds", which could point instead to the CI page Building guide: https://ghc.haskell.org/trac/ghc/wiki/Building Could have a link to the CI page. That "Nightly builds" heading points to http://haskell.inf.elte.hu/builders/, which is utterly opaque to me. It needs a wiki page explain what all this means. I'm sorry that I keep bleating (daily!) about writing up on the wiki, but it's really key to helping new people feel part of the story and able to contribute. The button on the home page is good too, but a) it only helps if you have some idea what Travis is. Otherwise it's just noise b) it only helps if you know how to interpret the page you get to when you click it, which I don't. c) I never look at the home page. I look at "status" or "building" or whatever from the LH column. The CI page could explain all that. Simon | -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of | Joachim Breitner | Sent: 12 July 2014 18:05 | To: ghc-devs | Subject: Travis now tests ghc directly | | Hi, | | I just added a .travis.yml file to GHC master. This means that every | push will be validated automatic and for free by travis; you can check | the build status at https://travis-ci.org/ghc/ghc/builds | | It is not a full validation. In particular, | * it skips DPH | * it does not build dynamic libraries and no dynamic executables | * does not build haddock or generate documentation | * only runs fast tests, and no performance tests | | This way we stay under the 50 minuite limit. | | Failures are reported to me, and I’ll manually report relevant breakage | to you. It is also configured to mail to ghc-builds@haskell.org, but I | don’t see these messages there. Maybe some mailing list admin needs to | whitelist mails from Travis CI ? | | I’ve also added a link to it from http://ghc.haskell.org/trac/ghc/, | including a nice icon showing the current build status. | | If you have that .travis.yml file in your branch, travis will also test | these. | | My unofficial ghc-complete repository is therefore obsolete, I stopped | updating it. | | Greetings, | Joachim | | | | -- | Joachim “nomeata” Breitner | mail@joachim-breitner.de • http://www.joachim-breitner.de/ | Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F | Debian Developer: nomeata@debian.org