Continuous Integration without Microsoft Team Foundation Server

I am not a fan of These Technologies whereas it is better to get familiarize with these technologies as well.

Continuous integration (CI) is the implementation of a process for continuously verifying whether a piece of software is working. CI provides developers with feedback about whether the piece of software compiles, passes all kinds of tests, builds into deliverables, and so on. It alerts the developer when changes he or she has just committed caused the build to fail, allowing the developer to correct errors while it's still fairly painless. Integrating changes late in the software development process can be costly and it often leads to errors.

This article presents the essential practices for implementing CI in your software projects, using the process we employed at my company, TouK, as an example. We implemented CI using the following open source tools, which we gradually adopted over time:

• Source code management:
  • Subversion
  • Git
• Repository for caching external libraries and storing released software (definitive software library):
  • Artifactory
  • Nexus
• CI server:
  • CruiseControl
  • Hudson
  • Jenkins
• Quality management platform:
  • Sonar

You can see how they interact in Figure 1 below. There are alternative implementations of these tools and open source products should easily integrate into an ecosystem like this.

 

Extracted From - http://www.devx.com/enterprise/Article/48297?trk=DXRSS_LATEST