Neil Mitchell

Thanks for the offer. Did you see the warning at https://github.com/ndmitchell/bake#readme? > Warning: This project is not actively developed - you are likely to be better of using something more...

Very reasonable questions, and ones that anyone wanting to look at Bake should be aware of, so I wrote a blog post answering them: https://neilmitchell.blogspot.co.uk/2018/05/the-end-of-bake.html. Let me know if there...

I've just updated the README to say that Bake is basically not developed anymore. There's nothing fundamental stopping Bake running on multiple targets at once, it should be a reasonable...

Bake makes the assumption that all patches are unique, so even if it doesn't check the store when submitting, it's still going to check the store to see if the...

Take a look at https://github.com/ndmitchell/bake/blob/master/src/Development/Bake/Core/GC.hs#L20, which exports a function `garbageCollect`, and explains its arguments. Running that every 20 minutes in a loop seems reasonable. I don't call `bake gc` anymore,...

`bake gc` works on the client or the server - it will GC whichever disk you run it on - we currently do both server and client. Running it as...

I'll leave this issue to document how to do it - the information from this ticket should be duplicated somewhere.

The model for doing Windows and Linux tests is that you have multiple tests, typically parameterised (e.g. a pair of `OS` and `Test`), and some tests get run by one...

No requirement at all to allocated clients to tests - the Brains module does that all at all. The provide/require stuff is to limit decisions, if you leave it all...

It won't aim for all clients to do everything - it aims to do everything once, but if a client is otherwise idle, it will do whatever it can, with...