title: Build Server Best Practices
body: <p>I heard google has some automated process like that:</p>
  
  <ul>
  <li>When you check in, your code is checked into a temporary location.</li>
  <li>It is built.</li>
  <li>Style checks run.</li>
  <li>Tests run.</li>
  <li>If there are no problems, code goes to actual repository.</li>
  <li>You receive an e - mail containing test results, performance graphs, style check results and whether your code is checked in.</li>
  </ul>
  
  <p>So if you want to learn if you broke something or the great performance gain you expected occurred, you just check in and receive an e - mail telling you what you need to know.</p>
  
  <p>What are your favorite build server best practices?</p>