Home > General > Upgrading CruiseControl

Upgrading CruiseControl

June 20th, 2007

I recently upgraded the version of CruiseControl that my team has been using from 2.2 to 2.7. I learned a few things that I haven’t really seen posted anywhere else. Most of these are common sense, but I will list them here mostly so the next time I do an upgrade I won’t forget.

  • Delete everything except for the *.ser files and the logs directory. The *.ser files are what hold the last build number for a particular project. This prevents your build number from going to back to 1 the next time it builds on the new version of CC
  • Don’t change the name of a project in the config.xml file. This will change the name of the corresponding *.ser file and will result in a build number of 1
  • You must have CVS or SVN installed and on the path in order for these commands to work within CruiseControl. This is definitely true for a Windows machine where these are less likely to be installed by default.

As I said, all common sense, but still very important to keep in mind when working with CruiseControl.

Categories: General Tags:
Comments are closed.