Thanks for your answers! From reading these links, it is still not clear to me if this might be overkill for my requirements. AB Cluster Setup talks about "*the worker requires 2+ TB to hold all the build temp files and git repos. If build artifacts and a local sstate mirror are included, additional worker space is required.*"
Currently, my build only takes 35GB, so I think what these links are talking about is how to replicate what the Autobuilder project https://autobuilder.yoctoproject.org/ already does. To clarify, I am not interested in running builds and tests for everything that Yocto already builds and tests (i.e. all the processor architectures, all the machine types, etc.). I am interested in running one build for one machine type (the Variscite DART-6UL i.MX6UL arm-based processor, for which NXP/Freescale and Variscite have provided recipes and layers for). I know that autobuilder includes BuildBot (this is why I specified it in parentheses) but my question remains: do I only install BuildBot and try to build my machine type with it, or do I install Autobuilder? On Mon, Nov 14, 2016 at 10:10 AM, Bill Randle <[email protected]> wrote: > Also, be sure to check the Yocto Project wiki pages: > https://wiki.yoctoproject.org/wiki/The_Yocto_Autobuilder > in particular, the AB cluster setup and AB maintenance links. Even > though the one link refers to setting up an entire cluster, I've used > that procedure to setup a single autobuilder, as well. > > -Bill > > On Fri, Nov 11, 2016 at 10:37 AM, Beth 'pidge' Flanagan > <[email protected]> wrote: > > On Fri, 2016-11-11 at 12:35 -0500, Alain Achkar wrote: > >> Hello Joshua! > >> > >> We are using Yocto to build for the Variscite DART-6UL SoM which is > >> based on Freescale/NXP i.MX6UL (http://variwiki.com/index.php?title=D > >> ART-6UL_Yocto_Jethro_R1_build). > >> > >> Currently, developers run builds manually on their desktops. We are > >> considering using a continuous integration server. I found out that > >> The Yocto Project uses Autobuilder which in turn uses BuildBot. I > >> read most of the introductory documentation. > >> > >> Would you recommend that we install only BuildBot and configure it to > >> build what we need? > >> > >> OR > >> > >> Would you recommend that we install Autobuilder (and BuildBot) and > >> configure it to build what we need? > > > > Actually, the yocto-autobuilder already contains buildbot so no need > > for both. > > > > If you read: > > > > http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/tree/README-QUIC > > KSTART > > > > and probably some of the other READMEs and the documentation in the > > docs directory of the yocto-autobuilder directory, it should get you > > started in the right direction. > > > > Feel free to ask questions if you need help. > > > > -b > > > > Elizabeth 'pidge' Flanagan > > Founder/CTO Togán Labs > > www.toganlabs.com > > > >> > >> What is the faster path to get up and running? > >> > >> Thanks! > >> Alain. > >> > >> -- > >> Alain Achkar, M.Eng. | Software Engineer > >> Triacta Power Solutions > >> (O) 613.256.2868 (C) 613.406.6520 > >> www.triacta.com > > > > > > > > -- > > _______________________________________________ > > yocto mailing list > > [email protected] > > https://lists.yoctoproject.org/listinfo/yocto > -- Alain Achkar, M.Eng. | Software Engineer *Triacta Power Solutions* (O) 613.256.2868 (C) 613.406.6520 *www.triacta.com <http://www.triacta.com/>*
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
