canonical-ci-engineering team mailing list archive

[Alexander Sack <asac@xxxxxxxxxxxxx>]

Right,

instead of touch_mir, call the saucy-proposed channel one "touch_saucy".

For now lets run default, install-on-boot and unity8 for touch_sf4p.

Also would be good if we rename touch_mir -> to touch (tracking
devel-proposed) instead of creating a new test so we dont loose
history.


On Fri, Oct 18, 2013 at 5:58 PM, Paul Larson <paul.larson@xxxxxxxxxxxxx> wrote:
> Hi Alex, following on to our discussion in IRC, I wanted to make sure
> everyone was in agreement with what we're proposing to do for saucy and
> trusty touch jobs going forward.
>
> == Current jobs we were running on Saucy ==
> touch_mir
> touch_ro (better described as surfaceflinger jobs, but renames are hard on
> the dashboard side)
> touch_custom
>
> == Proposed new jobs on Saucy ==
> touch_mir - saucy-proposed channel, we'd like to keep the same name just on
> Saucy if at all possible
>
> == Proposed new jobs on Trusty ==
> touch - Full run of tests on devel-proposed
> touch_sf4p - minimal run of TBD tests only on devel-proposed with mir turned
> off
> touch_custom - minimal run of the same tests we run now on custom jobs, but
> on trusty
>
> Andy, Joseph and I just had a hangout to sort out some of the technical
> details of what will be needed to do this, but we'd like to get confirmation
> that this is what you're expecting. The other thing I want to clarify, is
> which devices we run on. When we first started discussing whether to run on
> sf on irc, Ricardo was suggesting to just do it for tablets, but I think you
> are saying to do it on phones.  Do we run everything on phones only still?
> Do we need to add the tablets in for some tests again now?
>
> Thanks,
> Paul Larson