Re: [Ccnet-user] How to manage auto-incremented build number

[Mike R. <mik...@th...>]

Hi Alex,

Alex Chang wrote:

> <>Currently we have CruiseControl.NET configured to build with NAnt 
> and also using the DefaultLabeller feature to increment the build 
> number from CruiseControl.NET and passing it down to NAnt with 
> ${label-to-apply}.  Now we have two questions regarding this: 
>
> 1. Is there still not a way to get the version number that's generated 
> NAnt instead of using DefaultLabeller?  NAntContrib has "version 
> <http://nantcontrib.sourceforge.net/help/tasks/version.html>" task 
> that can do the versioning in NAnt.  But as far as I know there is no 
> way to pass this build number from NAnt back to CruiseControl.NET 
> right now (Or has anyone developed a tool for this?).
>
No, there is no way to do this. CCNet generates its own build numbers.

> 2. If we continue to use CruiseControl.NET DefaultLabeller feature to 
> increment the build number.  What is the best way to manage the 
> "major.minor.build.revision" (e.g 1.0.0.1  or just 1.0.0)?  Since the 
> DefaultLabeller only increments one digit (if we have 1.0.0. as the 
> prefix), should we be manually incrementing the other digits (major, 
> minor,..etc)?  And if we do move up the next level digit in the build 
> number (from 1.0.0.xx to 1.0.1.xx), how do we reset the 
> DefaultLabeller to start from 0 again?
>
If you want CCNet to include your full build label, you can use the 
Default Labeller, and specify a prefix, e.g. '1.0.0.' , see 
http://confluence.public.thoughtworks.org/display/CCNET/DefaultLabeller.

When you want to change your minor revision, you can change the prefix, 
and (for now) manually change the build number in your project's 'state' 
file (which is ccnet.state, by default).

But you don't have to get CCNet to think about your full build label-  
you can generate it in your NAnt script by concatenating 2 properties 
together, and then use something like <asminfo> 
(http://nant.sourceforge.net/help/tasks/asminfo.html) to generate your 
assembly info file.

In terms of resetting your CCNet build number, does it really matter if 
(for example) the next version after 1.0.0.123 is 1.1.0.124 instead of 
1.1.0.0?

The build label issue is something we're going to address in the future, 
see my recent coment at http://jira.public.thoughtworks.org/browse/CCNET-90

Mike