We should have a nightly (or similarly periodic) build and/or test run.
There are two basic options for this; one is using a huge Java blob download like Jenkins that's a whole project to set up and maintain, and the other is using a couple hundred lines of shellscript. The former is the github-era way; the latter is the "legacy" way where things are simple and effective...
Either way the thing should check out and build the Barrelfish tree (and the bintools tree, and any other trees we end up working on) and run the test suites for everything.
Automated testing for kernels, however, is its own thorny problem. It's annoying enough to do with an emulator; it's worse trying to use real hardware. Setting this up is probably a second project and probably isn't going to happen right away. We might be able to borrow some of the software infrastructure from ETH, maybe,
We should have a nightly (or similarly periodic) build and/or test run.
There are two basic options for this; one is using a huge Java blob download like Jenkins that's a whole project to set up and maintain, and the other is using a couple hundred lines of shellscript. The former is the github-era way; the latter is the "legacy" way where things are simple and effective...
Either way the thing should check out and build the Barrelfish tree (and the bintools tree, and any other trees we end up working on) and run the test suites for everything.
Automated testing for kernels, however, is its own thorny problem. It's annoying enough to do with an emulator; it's worse trying to use real hardware. Setting this up is probably a second project and probably isn't going to happen right away. We might be able to borrow some of the software infrastructure from ETH, maybe,
However, we should get the builds running pronto.