CI $Build.BuildNumber$ and Repo change best practic

Continua CI Discussion
1

What would be the recommended approach to the version counter $Build.BuildNumber$ and recording that change in the source control repository?

Continua has actions that allow you to change the assemblyinfo.* file to increment this. Cool, but I have some CI process questions around this.

Questions

1. As good source control citizens should we be committing that change version increment into the source control?

2. If we do submit a repository change as part of the Continua build process, how can we "discard" those changes from triggering another build?  How do you use Conditions to ignore repository change sets to files named AssemblyInfo.* or *.dnn, where I will need to periodically "hand increment" changes.  I couldn't find a good example in the wiki documentation http://wiki.finalbuilder.com/displa...Conditions

2

Hi Jamie

Some people commit changes to the file, some don’t. In our build processes we do not, we never release anything other than what comes out of a build machine (releasing of a dev machine is not allowed!). FWIW, Continua currently does not have the ability to commit changes to a repository. I’m in two minds as to whether it is needed or not.

As for ignoring the changes made during the build process, the repository has an Exclude Pattern tab where you can specify which files to ignore (changesets that only contain excluded files will be discarded).