On Mon, 2020-09-07 at 16:55 -0400, Tom Rini wrote: > On Mon, Sep 07, 2020 at 02:59:41PM -0300, Otavio Salvador wrote: > > Hello all, > > > > Em seg., 7 de set. de 2020 às 13:14, Richard Purdie > > <[email protected]> escreveu: > > > ... > > > Any thoughts from anyone on this? > > > > I second this and at least at O.S. Systems we've been using Docker > > containers to keep maintenance easier for old releases. I'd be > > great > > we could alleviate this and reduce its use as much as possible. > > > > The CI builder maintenance is indeed a time-consuming task and as > > easier it gets the easier is to convince people to set up them for > > their uses and in the end, this helps to improve the quality of > > submitted patches and reduces the maintenance effort as well. > > Excuse what may be a dumb question, but why are we not just building > pyro for example in a Ubuntu 16.04 or centos7 (or anything else with > official containers available) ? Is the performance hit too much, > even with good volume management? And extend that for other branches > of course. But as we look at why people care about such old releases > (or, supporting a current release into the future) it seems like "our > build environment is a container / VM so we can support this on > modern HW" pops up.
The autobuilder is setup for speed so there aren't VMs involved, its 'baremetal'. Containers would be possible but at that point the kernel isn't the distro kernel and you have permission issues with the qemu networking for example. Speed is extremely important as we have about a 6 hour build test time but a *massive* test range (e.g. all the gcc/glibc test suites on each arch, build+boot test all the arches under qemu for sysvinit+systemd, oe-selftest on each distro). I am already tearing my hair out trying to maintain what we have and deal with the races, adding in containers into the mix simply isn't something I can face. We do have older distros in the cluster for a time, e.g. centos7 is still there although we've replaced the OS on some of the original centos7 workers as the hardware had disk failures so there aren't as many of them as there were. Centos7 gives us problems trying to build master. So this plan is the best practical approach we can come up with to allow us to be able to build older releases yet not change the autobuilders too much and cause new sets of problems. I should have mentioned this, I just assume people kind of know this, sorry. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1165): https://lists.openembedded.org/g/openembedded-architecture/message/1165 Mute This Topic: https://lists.openembedded.org/mt/76689895/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
