Hi, When I was comiling the stage1 cross-compiler, I just wrote a bash script to be a cron-job that checks out, and runs, the RTEMS Source Builder
http://www.rtems.org/wiki/index.php/RTEMS_Source_Builder and it checks out the source each time from 0, it has some logging features that might meet your needs. Thanks, Cindy ________________________________________ From: gcc-cfarm-users-boun...@gna.org [gcc-cfarm-users-boun...@gna.org] on behalf of Jan-Benedict Glaw [jbg...@lug-owl.de] Sent: Tuesday, September 10, 2013 1:47 PM To: gcc-cfarm-users@gna.org Subject: [Gcc-cfarm-users] Build Robots Hi! Just got my account on the compile farm these days. Right now, I'm running a build robot building stage1 cross compilers, to catch simple build problems as a first step: http://toolchain.lug-owl.de/buildbot/ http://toolchain.lug-owl.de/buildbot/timeline.php People hinted/asked me to utilize cfarm machines, and to probably extend it to also do native builds and run the test suite. I guess that some of you already have comparable things running, so it would be nice to discuss some "lessons learned" early. Right now, I'm having two topics that I'd like to discuss. Job Dispatching ~~~~~~~~~~~~~~~ My first issue is job scheduling. I've had a look at some Continuous Integration (CI) systems (eg. Buildbot and Jenkins, just to name two popular ones), which both require additional stuff on a build client. (Jenkins even a working Java installation.) Right now, I tried to keep things simple and just wrote a shell script to do the actual building. It's called via ssh with only the target as an argument, its output is taken from the ssh pipe. Well-working in the current situation, but that'll not be enough to also fetch generated stuff (like test results). I'd probably also want to split the log output into logical pieces (ie. separate "./configure", "make", "make install" etc.), which is cumbersome at least right now. As a real solution, I think issueing the single steps as single commands over ssh would be the way to go. Porbably using libssh if this helps to get out of the quoting hell. Do you have experience with other CI systems you could recommend? SCM Update ~~~~~~~~~~ Right now, I'm using GIT for the three slaves I'm operating. Space consumption is reasonable and updates are *fast*. (Though the GIT repos lag behind the SVN and CVS repos by about half an hour.) Since doing a full check-out each time is no option on the compile farm, and space may be really limited, how do you share common source code right now? Are there eg. fast-updated GIT repos on some machines available that could be used as a shallow clone? Are you playing some tricks with SVN? So, how are you, how shall I keep a source tree for binutils/gcc around? Especially on the machines with little storage, which are probably the most interesting machines to actually build on... Thanks, Jan-Benedict -- Jan-Benedict Glaw jbg...@lug-owl.de +49-172-7608481 Signature of: If it doesn't work, force it. the second : If it breaks, it needed replacing anyway. _______________________________________________ Gcc-cfarm-users mailing list Gcc-cfarm-users@gna.org https://mail.gna.org/listinfo/gcc-cfarm-users
