<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5">
><br>
> At the moment buildbot fails with<br>
> "exceptions.RuntimeError: Couldn't find executable for<br>
> 'svn'"<br>
><br>
> + the same for git<br>
><br>
> I added ~buildbot/.bashrc to hopefully add Fink stuff<br>
> to buildbot's environment<br>
><br>
> .hc<br>
><br>
><br>
> Hmm, didn't work out, and<br>
> net.sourceforge.buildbot.plist has sw/bin in the path<br>
> too, and svn is there, so i really don't know...<br>
><br>
> Andras<br>
><br>
><br>
> Ok, I was getting some builds from macosx104-i386, but then it<br>
> disappeared, donno what happened there. macosx104-powerpc<br>
> seems to be running still tho.<br>
><br>
><br>
> Yea the process died somehow. I have restarted it with the command:<br>
> /sw/bin/buildbot restart /Users/buildbot/macosx104-i386<br>
><br>
> The output had some complaints:<br>
> /sw/lib/python2.6/site-packages/twisted/persisted/sob.py:12:<br>
> DeprecationWarning: the md5 module is deprecated; use hashlib instead<br>
> import os, md5, sys<br>
> /sw/lib/python2.6/site-packages/twisted/python/filepath.py:12:<br>
> DeprecationWarning: the sha module is deprecated; use the hashlib<br>
> module instead<br>
> import sha<br>
> /sw/lib/python2.6/site-packages/twisted/internet/_sslverify.py:5:<br>
> DeprecationWarning: the md5 module is deprecated; use hashlib instead<br>
> import itertools, md5<br>
> Following twistd.log until startup finished..<br>
> /sw/lib/python2.6/site-packages/buildbot/scripts/logwatcher.py:52:<br>
> PotentialZombieWarning: spawnProcess called, but the SIGCHLD handler<br>
> is not installed. This probably means you have not yet called<br>
> reactor.run, or called reactor.run(installSignalHandler=0). You will<br>
> probably never see this process finish, and it may become a zombie<br>
> process.<br>
> env=os.environ,<br>
> Removing stale pidfile /Users/buildbot/macosx104-i386/twistd.pid<br>
><br>
> I worked on the pd-master/master.cfg a bit, including changing<br>
> some of the names to be more consistent. I also got pure-data<br>
> building from Miller's git.<br>
><br>
> <a href="http://128.238.56.50:8010/builders/pure-data%20Linux%" target="_blank">http://128.238.56.50:8010/builders/pure-data%20Linux%</a><br>
> 20debian-stable-i386/builds/6<br>
><br>
> .hc<br>
><br>
><br>
> Good! I saw you stared experimenting with a builder for the externals<br>
> too - do i understand right that at the end we will have every<br>
> external built separately? I was thinking about breaking them out to a<br>
> separate master, but then we'd need to duplicate every slave setup, so<br>
> finally i think they could stay in the main master, and we could have<br>
> each of their have their own "category" name, which allows for some<br>
> selection at the web page.<br>
> Also note that for the builders, you can define an array with<br>
> "slavenames:" instead of a single string "slavename", so you can test<br>
> the same builder on multiple slaves at the same time. At the end they<br>
> have to broken down to one slave per builder, otherwise the diag<br>
> output is not easy to understand.<br>
><br>
> Changing descriptionDone values to past tense like "compiled" may not<br>
> make sense when the step fails and the output goes like "compiled<br>
> failed". Also there are things like "autogen" which don't have a<br>
> proper past tense... :)<br>
> Another thing i noticed an "svn update" by itself, i think we shall<br>
> have the sources explicitly in master.cfg otherwise it will fail where<br>
> the slave got reset. Also you told before we wanted "clobber" (tabula<br>
> rasa) checkout not an update...<br>
> I saw the "make install", "make uninstall" steps in the output -<br>
> having these would make much sense, fyi tests can be called with<br>
> Test() which has some advantages over ShellCommand() like it doesn't<br>
> make the whole build halt on failure.<br>
> BTW switching the sources to git is easy, what we have to work out is<br>
> Git polling. It's built into 0.8.1 but needs to triggered from git for<br>
> 0.7.12. And then we have this thing with the poller to explain it<br>
> which builder to start upon updates... a.k.a. the cake :)<br>
><br>
> Andras<br>
<br>
</div></div>One approach would be to use multiple PBChangeSource things and have<br>
commit hooks report to buildbot that they should build:<br>
<br></blockquote><div><br>Actually there is only one PBChangeSource needed/possible because it's a listener, and multiple commit hooks can communicate with it from the repos.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Another promising thing is loki, a web interface for easily setting up<br>
master/slaves:<br>
<br>
<a href="https://fedorahosted.org/loki/" target="_blank">https://fedorahosted.org/loki/</a><br>
<font color="#888888"><br>
</font></blockquote></div><br>Hm. Seems a bit young to me...<br><br>I see that at the moment every factory is "under construcion" so i won't touch the config file for a while so that you can edit around. (Which makes me think about putting it in svn later...)<br>
<a href="http://128.238.56.50:8010/one_box_per_builder">http://128.238.56.50:8010/one_box_per_builder</a><br clear="all"><br>Andras<br>