Reputation: 15988
I've just moved a large project out of a legacy version control system, and into Mercurial. I'm now faced with the task (opportunity!) of overhauling my old build system to work with this new source control system.
Are there any good build systems that:
that are already out there? As much fun as building and maintaining yet another build system might be, I'd rather reuse a mature, stable product and get back to developing my own code. :) If no tool exists with Mercurial in mind, what else might meet the requirements? What else might be out there that I'm forgetting?
Upvotes: 3
Views: 345
Reputation: 78350
Usually your build tool/system and your continuous integration system are separate, and the later is the one that knows about your DVCS system. In my setup the build tool is sbt (formerly ant) and the CI system is Jenkins (which I highly recommend).
The CI system speaks Mercurial, but it doesn't have to speak much of it. Mercurial lets you create URLs that track a specific named branch or tag, and so long as your CI system can clone/pull you're set. Once the CI system has updated to the version you want to build then it triggers you build system, which needs only look at the working directory.
Upvotes: 2