Whatever happened to those culprit emails? I thought those curbed the whole issue of forgetting to run a freshStart all.junit. I remember I was the first one to get one of those emails. I think I only forgot to run a freshStart all.junit a few times after that.
austen On 2/20/07, 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. just a thought. thanks, Aaron At 01:19 PM 2/20/2007, Philip Johnson wrote: >--On Tuesday, February 20, 2007 10:18 AM -1000 Pavel Senin ><[EMAIL PROTECTED]> wrote: > >>That's just checkstyle don't like lines longer than 100 symbols. >>I did run JUnit tests to see if everything works, and forgot about >>checkstyle. > >Just a friendly reminder: please do > >ant -q freshStart all.junit > >before committing. This runs both checkstyle and junit. Prior >experience shows that doing a freshStart all.junit tends to prevent >50-80% of our daily build failures. > >Cheers, >Philip
