On Mon, 20 Jun 2011 12:10:08 +1200, Michael Hudson-Doyle <michael.hud...@linaro.org> wrote: > 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...
I think it's vital for LAVA to connect a test run and the results from it, and I'm sure it will, but the details of that are something for you to decide. As a consumer of LAVA though I think it's also vital that there is some way to link to a particular test run for things like android-build.linaro.org. One way to do this would be to provide a test id back as the response to the API calls that schedule tests. That test id can then be used to contstruct URLs or make API calls. If you don't want test ids to be the basis of APIs etc. then we could also make use of something that worked based on an externally defined identifier (e.g. the android-build.linaro.org URL.) If we could make API calls specifying our identifier, and maybe construct URLs too then we can also use that to display results or whatever on android-build.linaro.org. In terms of implementation I think that the latter would be easier given where android-build.linaro.org is now, but I don't think the former would be that much harder for us to do. As for android-build.linaro.org building other things I don't think that's really an issue for LAVA, as I think that we should push from android-build.linaro.org to LAVA, rather than having LAVA pull. android-build.linaro.org can then decide based on the build type what info to submit, including the type of artifacts, and LAVA can have a simpler job to map from say "android" to the set of tests to run for that. Thanks, James _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
