Have you guys thought about having a script (that might use the same mechanism this patch uses for prebuilding the tests) that will produce test packages with all the binaries bundled that could then be normally used with autoserv, the scheduler and the web interface? That way you could just setup some recurrent jobs on the web interface and profit...
Of course, it would be necessary to find a way to make the client just skip the build stages for every test... Just an idea that occurred to me. 2010/2/9 Sean O'Connor <[email protected]>: > +1 to using an event driven push process vs cron for our prebuild needs... > > On Tue, Feb 9, 2010 at 12:54 PM, Martin Bligh <[email protected]> wrote: >> On Tue, Feb 9, 2010 at 12:48 PM, Eric Li(李咏竹) <[email protected]> wrote: >>> Yes, it will be useful before when people calling autoserv. And chromeos >>> dev only runs autotest through autoserv for now. We are in the middle of >>> setup the server. >>> >>> For a full server + scheduler situation, I am foreseeing to setup a cronjob >>> to periodically prebuild all client tests, and start up the scheduler from >>> the perbuild client directory. But I am open to other suggestions. >>> I do not want to setup prebuild per scheduled job. >> >> we should already have a hook to push to the packaging server on demand >> whenever a test updates ... should just be able to connect it in there? >> >>> On Tue, Feb 9, 2010 at 11:32 AM, John Admanski <[email protected]> wrote: >>>> >>>> What's the expected usage of this, in a setup where you have things like a >>>> scheduler? Right now this is only useful for running tests directly via >>>> autoserv; are there plans to expose this parameter to be useable in a full >>>> server+scheduler setup? >>>> -- John >>>> >>>> On Tue, Feb 9, 2010 at 9:50 AM, Eric Li(李咏竹) <[email protected]> wrote: >>>>> >>>>> Dear autotest committees: >>>>> The new flag will prebuild all autotest client tests/site_tests on the >>>>> server side, when the dev tool chain is not available on the client, by >>>>> directly invoke the setup method() on the test. >>>>> If this flag is not provided on the command line (default behavior), >>>>> there should be no regression changes to existing usages. >>>>> If provided: >>>>> --setup=all will prebuild all client tests/site_tests. >>>>> --setup=A,B,C,.. will only build the comma separated list of tests >>>>> supplied. >>>>> This new flag does not work with any control file, instead, it works on >>>>> test classes. >>>>> Rick of failure: very low. >>>>> Please review. >>>>> -- >>>>> Eric Li >>>>> 李咏竹 >>>>> Google Kirkland >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Autotest mailing list >>>>> [email protected] >>>>> http://test.kernel.org/cgi-bin/mailman/listinfo/autotest >>>>> >>>> >>> >>> >>> >>> -- >>> Eric Li >>> 李咏竹 >>> Google Kirkland >>> >>> >>> >> > _______________________________________________ > Autotest mailing list > [email protected] > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest > -- Lucas _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
