Re: [CMake] continuous integration with CMake

2009-12-07 Thread Randy Hancock
Well, I'll put the xml here but keep in mind I've never edited it directly. Hudson is configurable entirely through the web interface. All I did was fill out a few text boxes to point it to the source repository, which scripts to run on a build, and which files to archive when it's done. Still, the

Re: [CMake] continuous integration with CMake

2009-12-04 Thread Bill Hoffman
Tyler Roscoe wrote: On Fri, Dec 04, 2009 at 12:09:09PM -0500, Bill Hoffman wrote: Right now we just don't do that. However, we do have continuous builds running on systems that wait for anything to be checked into the version control system. Then they do a build and test. But, we have no w

Re: [CMake] continuous integration with CMake

2009-12-04 Thread Tyler Roscoe
On Fri, Dec 04, 2009 at 09:00:14AM -0800, Tyler Roscoe wrote: > Thanks for the reply. I'm going to try to carve out some time to give > Hudson a test drive. Btw, Randy, are any of your Hudson configs or other setup scripts available somewhere for me to look at? Maybe you can send them to me off-li

Re: [CMake] continuous integration with CMake

2009-12-04 Thread Tyler Roscoe
On Fri, Dec 04, 2009 at 12:09:09PM -0500, Bill Hoffman wrote: > Right now we just don't do that. However, we do have continuous builds > running on systems that wait for anything to be checked into the version > control system. Then they do a build and test. But, we have no way > to ask for

Re: [CMake] continuous integration with CMake

2009-12-04 Thread Bill Hoffman
Tyler Roscoe wrote: The solution we currently have sounds a lot like your setup: a cron that updates the build scripts and then a cron that runs the build scripts. Maybe I'm overreacting a bit since my CMake projects are fairly immature and we still muck arouund with things quite a bit, but this

Re: [CMake] continuous integration with CMake

2009-12-04 Thread Tyler Roscoe
On Fri, Dec 04, 2009 at 08:53:19AM -0600, Randy Hancock wrote: > 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 s

Re: [CMake] continuous integration with CMake

2009-12-04 Thread Tyler Roscoe
On Thu, Dec 03, 2009 at 09:32:48AM -0500, Bill Hoffman wrote: > We are working on being able to drive builds from CDash itself. > However, it is not really that hard to manage the multiple test machine > cronjobs. What we do at Kitware is create a version controlled script > directory. Each m

Re: [CMake] continuous integration with CMake

2009-12-04 Thread 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 a

Re: [CMake] continuous integration with CMake

2009-12-03 Thread Bill Hoffman
Tyler Roscoe 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

[CMake] continuous integration with CMake

2009-12-02 Thread Tyler Roscoe
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_,