Скачать или смотреть Choosing Between Cruise Control .Net and Team Foundation Build: What You Need to Know

Discover the pros and cons of using `Cruise Control .Net` and `Team Foundation Build` for continuous integration and build automation, and find out which one suits your organization's needs better.
---
This video is based on the question https://stackoverflow.com/q/80120/ asked by the user 'codeConcussion' ( https://stackoverflow.com/u/1321/ ) and on the answer https://stackoverflow.com/a/80223/ provided by the user 'Nick Monkman' ( https://stackoverflow.com/u/14391/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: Cruise Control .Net vs Team Foundation Build

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 2.5' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 2.5' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Choosing Between Cruise Control .Net and Team Foundation Build: What You Need to Know

Setting up effective nightly and continuous integration builds is crucial for any development team aiming to enhance productivity and ensure code quality. If you find yourself facing a dilemma between using Cruise Control .Net (CC.Net) and Team Foundation Build (TFB), you're not alone. Many teams, especially those already invested in Team Foundation Server (TFS), grapple with this decision.

In this post, we'll explore both options and analyze their strengths and weaknesses to help you make an informed choice.

Understanding the Challenge

Your team wants to establish a robust continuous integration system. While you have a good grasp of Cruise Control .Net, TFS is already part of your organizational infrastructure. Management prefers utilizing TFS due to the financial investment made in it. This situation creates a conflict between comfort with a familiar tool and organizational direction.

An Overview of Each Tool

Cruise Control .Net (CC.Net)

Flexibility: Known for offering a highly customizable environment, CC.Net allows for bespoke notifications and the implementation of custom scripts.

User-Friendly: Familiarity and ease of use are critical factors for teams already adept in CC.Net.

Team Foundation Build (TFB)

Integration: A robust platform that integrates seamlessly with TFS, which can be beneficial if your organization relies heavily on TFS features and reporting.

Build Agents: The ease of turning any machine into a build agent is a hallmark of TFB, simplifying the process of scaling up your build capacity.

Why Choose Team Foundation Build?

If you lean towards TFB, here are some features that make it appealing:

Build Agents Simplified: Transforming any box into a build machine is straightforward, empowering greater flexibility in resource allocation.

Powerful Reporting: All build results, including tests, are stored in a SQL database. The use of SQL Server Reporting Services allows for robust reporting capabilities that can track build and test results over time, an advantage not inherently found in CC.Net.

Customizations with MSBUILD
You can achieve similar customizations as in CC.Net via MSBUILD, which might resonate well with teams familiar with build automation systems.

Concerns with Team Foundation Build

Despite its robust features, TFB isn't without its challenges:

C++/CLI Limitations: Running C++/CLI projects or certain unit tests requires having VS Team or Team Suite installed on the build agent, which can be cumbersome and impractical.

TFS Dependency: TFB requires a connection to the TFS environment, limiting flexibility if your organizational needs change.

When to Stick with Cruise Control .Net

For teams on the leaner side or those deeply embedded with CC.Net, it might make more sense to continue using it. It allows for greater customization and agility, and many teams have successfully developed their reporting solutions, mirroring those found in TFB.

Conclusion: Making Your Decision

Your choice ultimately depends on what your organization prioritizes:

If your company values extensive reporting, scalability, and full integration with TFS, go with Team Foundation Build.

If you prefer flexibility, customizability, and control over your builds and notifications, then stick with Cruise Control .Net.

Choosing the right tool can make a significant difference in your CI/CD process, so weigh your options carefully based on your team’s needs and comfort level.

In the end, regardless of the tool, remember that continuous integration is most effective when it aligns with your team's workflow and development culture.