--On Tuesday, February 20, 2007 10:46 PM -1000 Aaron Kagawa <[EMAIL PROTECTED]> wrote:
Here is a thought, why not run a freshStart all.junit (without any sensors enabled) every 10 minutes if there is a commit. Austen and I have found that we've come home to broken Hackystat builds, which just causes headaches when we decide to do some Hackystat hacking. Increasing the builds would also likely give us some more interesting insights to our build process. It will definitely detect more cases of developers forgetting to do freshStart all.junit before committing.
Yes, this would move us into a 'normal' continuous integration style of development, which has lots of advantages. The main stumbling block is reducing the time required for a freshStart all.junit for the hackystat-all configuration. I'd like to solve this through a combination of reducing the number of modules in hackystat-all and improving our build hardware.
It's an excellent suggestion. Hopefully people won't use it as an excuse to not do their own local freshStart all.junit!
Cheers, Philip
