ubuntu-phone team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

On Fri, Dec 20, 2013 at 6:47 AM, Sergio Schvezov
<sergio.schvezov@xxxxxxxxxxxxx> wrote:

> If no one deletes the jenkins job run itself, for the case of webbrowser
> app, all runs for mako are here:
> https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-webbrowser-app-autopilot/
>
>
>> For example, for webbrowser-app on image 77 on mako, the dashboard [1] is
>> all green, and so is the jenkins view [2].
>> Have the artifacts of the first two tries been kept somewhere?
>
>
> I'm not sure how this is configured, the policy on when to drop artifacts
> themselves in jenkins, but build 87 has failed runs
> https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-webbrowser-app-autopilot/87/
> and it's artifacts, under 'Build Artifacts' are still there.
>
> The only thing that doesn't look that easy to grab is match the jenkins job
> run with a specific build attempt from the ci side, unless it's already in
> one of the collected logs and I just can't find it.
The dashboard will always have results from the latest build of the
buildstamp you are looking at, unless it gets marked in the jenkins
description field with dash_ignore.  If you are looking for multiple
test runs on the same build, the easiest thing to do is to back up to
the job level in jenkins, for instance:
https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-webbrowser-app-autopilot/

If you look on that page, down the left hand side, you'll see that 78
and 79 were only run once when they were kicked off automatically by
the presence of a new build.  77 had to be run a few times over, so
you'll see it listed multiple times there.