VSoft Technologies Blogs

rss

VSoft Technologies Blogs - posts about our products and software development.

Pervasiveness of Continuous Integration

Do you currently use a Continuous Integration system?

Continuous Integration among FinalBuilder Users

 

Since releasing the full featured FBServer in April, we’ve seen healthy growth in its adoption as a Continuous Integration Server; however, the 2008 FB Survey showed quite low adoption of Continuous Integration systems in general among FinalBuilder users.

More importantly, of those not using any CI system, 2/3’s did not intend to start using a CI system in the next 12 months!

Do you plan to start using a Continuous Integration system within the next 12 months?

Future Continuous Integration adoption amoung FinalBuilder Users

For users of an automated build tool, most of whom have free access to a very easy-to-configure Continuous Integration server, these are incredibly low proportions! I can only speculate that perhaps the benefits of CI aren’t as well known, or appreciated, as the benefits of a fully automated build and release process.

 

---

This is the 3rd post in a series discussing insights uncovered in the 2008 FinalBuilder survey.

Related Posts


  • Continuous Integration Server performance

    Continuous Integration Servers are often underspecified when it comes to hardware. In the early days of Automated Builds, the build server was quite often that old pc in the corner of the office, or an old server in the data center that no one else wanted. Developers weren't doing many builds per day, so it worked, it was probably slow but that didn't seem to matter much. Fast forward 20 years, and the CI server is now a critical service. The volume and frequency of builds has increased dramatically, and a slow CI server can be a real problem in an environment where we want fast feedback on that code we just committed (even though it "worked on my machine"). Continuous Deployment only adds to the workload of the CI server. In this post I'm going to cover off some ideas to hopefully improve the performance of your CI server.

  • Automated Builds vs Continuous Integration

    Roy Osherove posted this video explaining the difference between Automated Builds and CI (ie, FinalBuilder vs Continua CI)

  • Continuous Integration with FinalBuilder

    In this post, I'm going to look at how to structure a FinalBuilder project so that it will run on your dev machine, or on your Continua CI Server without modification. This allows the best of both worlds, develop and debug your build process on your development machine, and then later run it on your CI server.

  • Continua CI and FinalBuilder integration improvements

    The updates to Continua CI and FinalBuilder released today provide somewhat better integration between the two products.

  • ClearCase integration for FinalBuilder

    Check it out (pun intended...) FinalBuilder now has very comprehensive integration for IBM/Rational ClearCase.

  • DUnit and FinalBuilder/FinalBuilder Server - better integration.

    FinalBuilder has had an NUnit action for some time now, but for DUnit we have always advocated just compiling the unit test executable as a console app using the TextTestRunner, and using the Execute Program action. This has worked fine, however it doesn't provide the same sort of integration into FinalBuilder Server as the NUnit action provides.

Continuous Integration
Showing 2 Comments
Avatar
Brent 16 years ago

As of the 6.1 release, StarTeam is now a supported VCS. :)<br><br>You can download 6.1 any time via the usual channels. <br><br>Enjoy!

Avatar
LSondergaard 16 years ago

Add StarTeam as supported for Continuous Integration and we will start using it :-)



Comments are closed.