On 21 Nov 2008, at 12:07 , Sebastien Lelong wrote: > 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... :)
Fine with me. > > 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... Again, when updating, I test again with hardware. Well, maybe not when adding a license.. --- ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands tel+31-546-491106 fax+31-546-491107 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
