On Tue, Dec 14, 2010 at 04:30, Naeem Sarfraz <[email protected]> wrote: > Hi Andy > > I had to write my own labeller to get the latest revision of the working > directory. It doesn't take much to write.
Where I'm getting hung up is that it's working for my development (CI) environment, but not my integration test. Why the difference? > > On 13 Dec 2010 21:51, "Andy Levy" <[email protected]> wrote: >> I have an application configured to be built on 3 servers: >> development, integration test & production. Source control is via >> Subversion. >> >> In development, I use the following labeler to name my tag after building: >> >> <labeller type="lastChangeLabeller" allowDuplicateSubsequentLabels="true"> >> <prefix>dev3_</prefix> >> </labeller> >> >> This works fine; after my last build, tag dev3_6312 was created in the >> project's tags directory at revision 6313 (no commits between the last >> commit and the completion of the build). >> >> In my integration test environment, I'm performing my first CCNet >> build, pulling from URL/TO/dev3_6312 to get my source code. I'm using >> the following labeler: >> >> <labeller type="lastChangeLabeller" allowDuplicateSubsequentLabels="true"> >> <prefix>test_</prefix> >> </labeller> >> >> I have attempted to build several times, and each time the tag created >> is test_unknown. >> >> How do I get the labeler to pick up the revision number? >
