Does CC.NET check for modification when the build script does the validation

Question

I’m doing some research to completely automate our development and there is still one grumbling question that I hope the StackOverflow community can solve for me.

I understand that IntervalTrigger, if configured correctly, checks VSS every X seconds for changes, and if it finds a modified file, my tasks will start. One of my tasks is to check AssemblyInfo files and update version numbers. After updating these files, they will be returned to VSS.

Thinking about this solution, this does not make much sense, because, in my opinion, I force the check for modified files to true every time the trigger fires. Am I missing something? Is there a way to do this without starting automatic assembly when registering AssemblyInfo?

Answer 1

You can use the Filtered Source Control Block to exclude certain files from the trigger.

Answer 2

I just posted a bunch of my default build process that might interest you: Solution for developing and deploying an SVN website

Answer 3

As I usually customize my projects using CC.NET, you need to have two project blocks for one solution. One of them is configured as an interval trigger, which does nothing more than retrieve the last from my repository, build a solution, and run unit tests. The other is a schedule trigger that does everything the other does, but actually publishes the assembly. This includes changing version numbers, publishing files, etc. This may work in your case, since a change in version will start the interval project, but only once.

Answer 4

Checking for automatically generated AssemblyInfo in a version control system is a bad idea, don't do this. You will get a lot of noise in your story (50% of all fixations!). In addition, it does not give you any new information - you can always extract it from VCS. Build your script collector to make these files a good practice, but do not revert these changes!