canonical-ci-engineering team mailing list archive

["Stephen M. Webb" <stephen.webb@xxxxxxxxxxxxx>]

On 15-09-08 05:58 PM, Kevin Gunn wrote:
> Whoa! 1.5 hrs longer.
> Per MP that'd probably be too painful as wait times have been an issue in the past, especially for Mir (not sure what
> we're down to, but i think it was ~30min at best).
> 
> Wondering (wanting Cemil/Stephen to chime in) would it make sense to have all MP's landing on development-branch running
> CI on 
> * vivid+overlay armhf (any real phone hw)
> * wily amd64
> 
> Then have promotions to release run on all the priority 1 configurations 
> * vivid+overlay armhf (any real phone hw)
> * wily amd64
> * wily armhf (any real phone hw)
> * wily i386
> 
> in order to avoid sinking so much time into every MP

I'd really rather see everything thrown at the MP CI so failures just don't make it as far as the archive.  Promotion to
release is not the time to start finding problems, that's the entire point of CI at the MP level.

Why would the builds be slowed down so much?  Is it just that the hardware is slow or is there a long delay waiting for
resources in general?

-- 
Stephen M. Webb  <stephen.webb@xxxxxxxxxxxxx>