Change operation flow in cruisecontrol.net for DVCS?

Question

The CruiseControl.NET operation flow, documented in the Operation flow of CCNet FAQ, where the label is generated first makes some sense for a centralized VCS but not so much for a DVCS. With a DVCS, it would be better to generate the label after getting the source because the source itself might be needed for the label (e.g., the .hgtags file in Mercurial or other local source files used to compute version and build numbers).

Has anyone figured out a way to run the CCNet labeller after getting the source?

Answer 1

We don't use the Labeller in CC.NET, but nevertheless, our approach might work for you as well:

• create a separate project MercurialCheckout that performs
  • Mercurial checkout
  • Executable task that updates a text file triggers/mercurial.txt on the build server
• change your "real" project from sourcecontrol type mercurial to sourcecontrol type filesystem, watching the triggers/directory

Your real project then includes the Labeller task, and since the Mercurial checkout was done before, the Labeller should generate the "right" label.

Kind regards Frank