Haha! Cool. I've got just the guy to help out. We've got a convert from ST Ericsson starting tomorrow and I think this'll be a perfect task for him to start with. Look for a contact from Frans Gifford. I'll CC you on my email to him. Would you create a BP named something like "connect the dots?"
-Zach On 19 June 2011 19:10, Michael Hudson-Doyle <michael.hud...@linaro.org> wrote: > On Sat, 18 Jun 2011 04:31:24 -0500, Zach Pfeffer <zach.pfef...@linaro.org> > wrote: >> On 18 June 2011 04:07, Zygmunt Krynicki <zygmunt.kryni...@linaro.org> wrote: >> > Michael is working on the scheduler. He recently added API for submitting a >> > job to the system. It's still some time before this can be used in >> > production though. AFAIR there is no code that would take jobs and actually >> > ask dispatchers to run them. >> >> Since we're got such low usage at the moment, is there any way we can >> start to use it without a full scheduler in place? For instance, Paul >> had mentioned that we could email him and he would kick off jobs. >> Perhaps we could just agree on times that android-build could request >> tests? Do a manual schedule? > > I have the guts of the scheduler written already. It doesn't really > have a UI and the error reporting is terrible and it probably has bugs, > but I think we should try to get this deployed ASAP and improve that > rather than invest time in band-aid type solutions (as I said in the > other email, I'll describe my progress later today). > > Actually doing the deployment is probably the sticking point of this. I > don't know much about the current set up we have, but AIUI we've kinda > shuffled our code around a bit since the last one so some things > probably need to change. I know Zygmunt has been working on tools to > build all our code into a PPA, so if that's nearly ready, can we deploy > lava-dispatcher in place of launch-control soon? Once that's done, > adding the scheduler to the mix will be pretty easy (the benefit of all > this shuffling). > > > Something I don't completely have a plan for in my head at the moment is > connecting the dots, or preserving identity between componenets (as I > think Zygmunt put it). We have a build, which will trigger a test run, > which will result in a test bundle being uploaded to the dashboard. I > can see how to link the build to the test run and (mostly -- I'd like to > talk about the details of this) see how to link the test run to the > bundle, but I don't quite see how to have a link on the build page that > goes straight to the results. I guess we can always have a > $job_url/results link that does a redirect to the appropriate page in > the dashboard... > > Cheers, > mwh > _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
