Michi, Apologies for not sending out a notification. This was actually completed some time ago. The branches lp:thumbnailer, lp:unity-scopes-api/devel and lp:unity-scopes-api are built on vivid and xenial in CI (and no wily).
But it looks like we missed lp:unity-scopes-api/devel. Is this the branch that causing the issues or is there a different problem that needs to be investigated? Francis On Wed, Nov 11, 2015 at 6:40 PM, Michi Henning <[email protected]> wrote: > Hi Francis, > > could we get this set up for unity-scopes-api at least? I ran into a > problem with our build tools yesterday that requires the xenial package to > resolve. > > Thanks, > > Michi. > > > On 24 Oct 2015, at 13:57 , Francis Ginther <[email protected]> > wrote: > > Michi, > > Your request is in progress. This depends on getting the xenial > infrastructure in place first which usually takes a few days. We will let > you know when this is ready. > > Francis > > On Thu, Oct 22, 2015 at 8:59 PM, Michi Henning < > [email protected]> wrote: > >> Hi guys, >> >> could you please switch our Jenkins builds for unity-scopes-api and >> thumbnailer to target Vivid and Xenial instead of Vivid and Wily? >> >> Thanks, >> >> Michi. >> -- >> Mailing list: https://launchpad.net/~canonical-ci-engineering >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~canonical-ci-engineering >> More help : https://help.launchpad.net/ListHelp >> > > > > -- > Francis Ginther > Canonical - Ubuntu Engineering - Continuous Integration Team > > > -- Francis Ginther Canonical - Ubuntu Engineering - Continuous Integration Team
-- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
