> The easiest would be a Seb-maintained "jallib server" where we have ssh access to. I could supply the hardware, but I don't know too much about Linux outside FreeBSD. > I might get a Ubuntu box up and running so Seb can ssh into it, if that is his favourite POSIX brand.
Ubuntu is ok for me, but I'm sure I'm ok with a Seb-maintained "jallib server"... > So the procedure would be as follows: > coder makes lib > coder tests lib > coder submits lib > buildbot agrees > coders ssh's into jallib server > coder adds test result to matrix With this, you can simplify the feed of the matrix. If the server runs an Apache or the like, a web interface is better: * coder logs in * there's a list of all libs & samples * he selects the one he tested * he says "yes it pass" or "no it fails" and validate Can be done in cherrypy for instance... :) > Again, if buildbot agrees with the code, it could spit out a file with good samples, which can then be auto-added to the test matrix. Again, how the bot knows if a sample runs or not ? If you mean the bot can use the matrix to auto-generate html pages, yes, it's possible . > This implies no one may upload code which has not been tested on the actual hardware, but we agreed on that already. If upload == commit, you'll have a problem when you update the code... Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
