Per, Wow - that is interesting. I don't believe that was the behavior before my upgrade - but it sure explains what I am seeing.
Let me change that parameter and see what happens. Thanks, - Ron On Jun 30, 4:59 am, Per-Jonny Käck <[email protected]> wrote: > Hi, > > You have set allowDuplicateSubsequentLabels to False, which means that > unique labels will be created by adding a suffix number after the change > number. > > Your first build with modifications for change number 853 will be: > 2.2.0.853.1 > If you then force a build without modifications the next label will be: > 2.2.0.853.2 > Your next build with modifications for change number 859 will be: > 2.2.0.859.1 > ... > > If you set the allowDuplicateSubsequentLabels to True, your build labels > will be created as: > Your first build with modifications for change number 853 will be: 2.2.0.853 > If you then force a build without modifications the next label will be: > 2.2.0.853 > Your next build with modifications for change number 859 will be: 2.2.0.859 > > //P-J > > 2009/6/30 Ruben Willems <[email protected]> > > > Hi > > > Do not find anything weird in the code for the moment, > > is this from a force build, or when modifications where detected? > > > with kind regards > > Ruben Willems > > > On Mon, Jun 29, 2009 at 11:54 PM, rifferte <[email protected]> wrote: > > >> I have the following code in one of my ccnet.configs: > > >> <labeller type="lastChangeLabeller"> > >> <allowDuplicateSubsequentLabels>False</ > >> allowDuplicateSubsequentLabels> > >> <prefix>2.2.0.</prefix> > >> </labeller> > > >> When I look at my buildlog file - I am seeing the following: > > >> <CCNetLabel>2.2.0.853.4</CCNetLabel> > > >> I am currently using Perforce. The 853 number is correct - as that is > >> the latest change list number. My expectation is that the CCNet label > >> would be out put as such: > > >> <CCNetLabel>2.2.0.853</CCNetLabel> > > >> I do not know where the ".4" is coming from. This started occurring > >> after our upgrade to 1.4 from 1.3. > > >> Any ideas?
