| 4 | | The GHC builder builds GHC on various platforms in various different ways each night, runs the test suite and performance benchmarks, and mails the results to the `cvs-ghc@haskell.org` mailing list. We're always keen to add more build slaves to the setup, especially if you have a platform that doesn't already have a build slave, so if you'd like to join the fun, please let us know at [mailto:cvs-ghc@haskell.org]. If a platform is represented in the nightly builds, it's more likely we'll be able to identify and fix problems specific to that platform quickly. |
| | 4 | The '''GHC builder''' is a client/server system that allows us to build and test GHC on lots of different computers scattered around the world (the ''clients'', or ''build slaves''), and aggregate the test results centrally (the ''server''). |
| | 5 | |
| | 6 | Each night we build GHC on each slave, in various different ways, run the test suite and performance benchmarks, and mail the results to the `cvs-ghc@haskell.org` mailing list. |
| | 7 | |
| | 8 | == Seeing build results == |
| | 9 | |
| | 10 | The build results are uploaded to http://darcs.haskell.org/ghcBuilder/builders/ |
| | 11 | |
| | 12 | == Can you offer a build slave? == |
| | 13 | |
| | 14 | We're always keen to add more build slaves to the setup. If a platform is represented in the nightly builds, it's we can identify and fix problems specific to that platform much more quickly. If you'd like to join the fun, please let us know at [mailto:cvs-ghc@haskell.org]. |
| | 15 | |
| | 16 | |
| | 17 | = How to set up a build slave = |
| | 18 | |
| | 19 | The GHC Builder is written in Haskell as a pair of Cabal packages (one for the clients/slaves, and one for the server). |
