[CMake] continuous integration with CMake

[Randy Hancock]

We use Hudson for c++ CI. It works very well for us. Just point it to
a script that kicks off the build (e.g. cmake --build) and have it
archive the artifacts (build logs, test output, etc.). I'm sure there
are fancier ways to set it up with plugins but we've gotten by with
this minimal setup for about 6 months now. It's so easy to get going I
recommend spending a few hours setting it up just to see if you like
it. That said, I have not tried CDash.

On Wed, Dec 2, 2009 at 11:18 AM, Tyler Roscoe <tyler at cryptio.net> wrote:
> I am using CMake to build several medium-sized C++ projects on several
> Linux and Windows platforms (with an eye to supporting Mac and several
> Unices eventually). The next step is to get a Continuous Integration
> envrionment up and running.
>
> From my readings around the web and in _Mastering CMake_, it seems that
> the CMake solution for CI is CTest + make Continuous + CDash, all run
> via cron or Scheduled Tasks with some sort of customized CTest script.
> That type of setup works, but maintaining it looks like a pain: I have
> to manage crons/Scheduled Tasks on dozens of machines. I have to keep
> track of which machine builds which products with some kind of manual
> logic. I have to figure out for myself how to schedule a one-off build
> as an experiment or for an emergency bugfix.
>
> How do other people handle this situation? Am I overcomplicating things?
> Are my needs more complex than what most people do?
>
> Am I missing out on some management tools for CI with CMake?
>
> Do people with more complex build needs use other tools on top of their
> CMake builds? For example, many build engineers seem to enjoy Hudson,
> especially for Java projects, but it seems like a less natural fit for a
> C++ project. I did find these links; anyone using this plugin?
>
> http://schneide.wordpress.com/2009/04/07/cmake-builder-plugin-for-hudson/
> http://schneide.wordpress.com/2009/11/09/cmake-builder-plugin-reloaded/
>
> Advice, whimsical anecdotes, or links would be appreciated.
>
> Thanks,
> tyler
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>