Hello, as far as i know Mercurial uses, like git, sha-1 hashsums as "commit identifier". The AssemblyVersionLabeller depends on numeric values, like svn revisions numbers.
Checkout your build log (from a IfModificationExist) build and have a look in the: <integrationProperties> section. Search for: <LastChangeNumber>7233</LastChangeNumber> In your case it is a sha-1 checksum, right? You can also check your ccnetservice.log file in debug logging mode. There the AssemblyVersionLabeller prints out what he is donig. Daniel Am 12.05.2010 20:14, schrieb cstavro: > I can't seem to get the AssemblyVersionLabeller to pull the numerical > revision number from the repository for the build label. > > According to what I've been able to find here (http:// > groups.google.com/group/ccnet-user/browse_thread/thread/ > 4baaf260c66be41c/ad3a6bfbc0d94dfa? > lnk=gst&q=assemblyVersionLabeller#ad3a6bfbc0d94dfa) this was > considered and agreed upon thus I assume it should work so I must be > missing something. > > Here's the relevant bit from the config: > > <sourcecontrol type="hg"> > > <repo>https://user:[email protected]/myproject/1.0-stable/</repo> > > <workingDirectory>C:\build\myproject\1.0-stable</workingDirectory> > </sourcecontrol> > <labeller type="assemblyVersionLabeller"> > <major>1</major> > <minor>0</minor> > <incrementOnFailure>false</incrementOnFailure> > </labeller> > > Right now my labels are coming out with 1.0.<build>.0 where build is > the CC incrementing build number. > > I'm in version 1.5.6804.1 > > Anyone have any suggestions on this one? >
