What is a private build? … a way to automate the local testing … Jim Wallace
  1. Clean the environment. All private builds must start from a clean environment and should not use any external assets from previous builds or any other source. This helps identify and prevent issues potentially caused by environmental discrepancies.
  2. Compile your entire solution/project all at once. The entire solution must build correctly. One issue, even a simple missing file in one component, should fail the entire solution until it is resolved and before a commit.
  3. Provide all dependencies necessary for running unit and integration tests. This is very important. It is what enables the actual continuous integration and deployment pipeline to run the tests during the appropriate environments.
  4. Runs all automated unit tests. They should be very fast and use no external resources. These tests should confirm that every function continues to perform as expected.
  5. Run component-level integration tests. These tests should confirm that the interaction and interfaces between the components continue to operate as expected. The industry standard is 10 minutes or less.
Confidence in your ability to deploy your software is best achieved by executing a private build before a commit David Walker

References & Resources

Learn how to create your own private build and more with theses resources:
  1. What is a private build?
  2. Using psake for Private and Integrated BuildsPowershell
  3. CakeC#
  4. FakeF#
  5. RakeRuby