Continuous Integration using FinalBuilder Server
Continuous integration involves building, testing and reporting on your software’s code as soon as changes are checked-in to your version control system. It is a foundation of agile development and provides many benefits, not the least of which is a clear indication of the status of your project at regular intervals.
Implementing continuous integration is simplified with FinalBuilder Server's source control triggers. Add a trigger to a FinalBuilder Server build project, configure its properties and you can easily set up continuous integration with:
- Accurev
- CVS
- Perforce
- StarTeam
- Subversion
- Surround SCM
- Vault
- Visual SourceSafe
- Visual Studio Team System
When properly combined with an automated build and test process, continuous integration with FinalBuilder Server provides instantaneous feedback about integration errors, allowing you to have a clear insight into the health of your project. All of this means continuous integration can help effectively improve the quality of your software and speed-up your development life-cycle.
The screen shot below shows just how easy it is to setup and manage a Continuous Integration trigger in FinalBuilder Server.
Despite being easy to set up, these continuous integration triggers unleash a huge amount of potential for improving your build process. Using them to achieve iterative development and get continuous feedback, your team will have a clear indication on the status of your project and corresponding quality of your development outcomes at every stage of the project.
If your version control system is not natively supported, FinalBuilder can support it using its command line interface. FinalBuilder's developers are also always adding native support for other version control systems in the future, so if you would like your VCS support, please contact us.