On Sun, Jul 3, 2011 at 9:13 PM, Zach Pfeffer
<zach.pfeffer@linaro.org> wrote:
Yeah. Those results seem rational. Would you test:
https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/#build=3
This one is currently running
https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-release/
This one is identical to the above
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release/#build=2
...and update the build note on each page with the validation results?
What is this build note and where is it displayed?
Here's how to update the description from Paul Sokolovsky:
1. Make sure you're registered with Jenkins:
https://android-build.linaro.org/jenkins/people/
2. If you aren't, sign up at
https://android-build.linaro.org/jenkins/signup and let me know your
username, so I can give you appropriate permissions (Zach, this point
is for you)
3. Browse to needed job from Jenkins frontpage:
https://android-build.linaro.org/jenkins/
4. Once you at job's page (e.g.
https://android-build.linaro.org/jenkins/job/linaro-android_beagle/),
click "add description"/"edit description" in the top right corner, and
edit the description. Full HTML is allowed.
5. Click Submit and see if it looks OK. Repeat editing if needed.
Otherwise, the description is immediately available at frontend's page
for the job. (Though for your own browser, you sometime need to Ctrl+R
it to refresh cache).
Is there an easier way of doing this? I don't think anyone wants to be doing this for every single test. Our goal was to automate this, so we really need a way to link the results back in some automated fashion, or they need to just be searched by the person looking for them.
Please add the validation stuff to the bottom.
I held off on this for the time being, pending the answer to my question above. This appeared to be a pretty generic place associated with the whole build, not that specific build id. Is there a better place to add it?
Would you do this for all validation results from builds we manual
request tested from here on out?
If it's one or two a month, sure. Or better yet, we'll soon be able to let you schedule your own jobs. We're deploying the new lava-server/lava-dashboard this week, and on top of that will be the scheduler as well. This would enable you to kick off your own jobs for one-offs like this.
Thanks,
Paul Larson