We are currently evaluating FB6 and are using CC.NET. It is working very well except for the following issue I have picked up below with regards to the "Auto Increment Build" property for a VS Solution action.
When in the FB application and a build is done, the build numbers are incremented correctly and the last build value used is stored.
but
When the build is triggered by CC.NET, the build numbers are incremented, but the last increment is not stored. Thus, when CC.NET triggers FB to build again, the same build numbers are used over and over.
Basically, it seem that when triggering FB to build from CC.NET, the last auto increment build number is not stored for the VS Solution action. We would always like the build number to be incremented by FB, be it in the IDE or called by CC.NET.
Thanks for your post. Is CruiseControl.NET automatically doing a Get of the files from source control? Is it grabbing the AssemblyInfo or .RC files for your solution(s)? If so, you'll need to check in these files as part of your build process (after the solution is built), so that the new build number is persisted to source control. Otherwise, next time around CC.NET will revert the files back to the old versions.
(Incidentally, you'll also need to tell CC.NET to ignore those particular files, so that checking in the changes doesn't trigger yet another build.)
I am basically just using CC.NET to tell FinalBuilder to do a build when a change occurs to the source in VSS. FinalBuilder then gets latest from VSS and does the build.
I am using FinalBuilder to keep track of build numbers and auto-incrementing of the build numbers. FinalBuilder overrides anything in the assembly info of the solution/projects (which is what I want to occur). The problem is that when FinalBuilder is triggered to perform a build from CC.NET, when FinalBuilder increments the build number and once the build is completed, the last build number is not persisted back to the FinalBuilder project file. Thus, when CC.NET tells FinalBuilder to build again, the same build number gets used over and over.
Oddly enough though, building within the FinalBuilder IDE, the build number is incremented and after the build, the last build number is persisted.
I have seemed to solved my issue. I added the “Save FinalBuilder Project” action as the last step if the build it succesful. Then the last build number gets saved.