All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alain Achkar <alain.achkar@triacta.com>
To: yocto@yoctoproject.org
Cc: joshua.g.lock@intel.com
Subject: Re: Buildbot / Autobuilder / custom?
Date: Thu, 23 Mar 2017 17:40:45 -0400	[thread overview]
Message-ID: <CAGkf0HCdi=Y00Aa=b=OqGVz0OL5N0cd4de6tK9CoDNv7P=Ee7A@mail.gmail.com> (raw)
In-Reply-To: <CA+n--H9FzfDocWHVemzRj49GpAFcQ=jCAfOyP7eJhikYw+H9nw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 9476 bytes --]

I followed
http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/tree/README-QUICKSTART
and got:

>0< alain@esxi-ub1 Thu Mar 23 05:34 PM [master]
/media/data/yocto-autobuilder >  *. ./yocto-autobuilder-setup*

Creating yocto-controller/buildbot.tac from an example buildbot.tac


Creating yocto-worker/buildbot.tac from an example buildbot.tac


Creating yocto-controller/controller.cfg from an example controller.cfg

#########################################################################
 Setting envvars.
 In the future though please add the following to your shell environment:
 PYTHONPATH=/media/data/yocto-autobuilder/lib/python2.7/site-packages/:/media/data/yocto-autobuilder/lib/python2.7/site-packages/autobuilder/:/media/data/yocto-autobuilder/lib/python2.7/site-packages/autobuilder/buildsteps:$PYTHONPATH
 PATH=/media/data/yocto-autobuilder/bin:/media/data/yocto-autobuilder/yocto-autobuilder/scripts:$PATH
 YOCTO_AB_CONFIG=/media/data/yocto-autobuilder/buildset-config/yoctoAB.conf

 If you don't, you should source this script everytime you want start the
 autobuilder.

Creating config/autobuilder.conf from an example autobuilder.conf


Creating buildset-config from buildset-config.controller


 You've not setup the autobuilder before. Generating a server/client
password
 combo for you.
 Client/Server Password = (deleted, on purpose)

 Modifying the following files with this password:

 /media/data/yocto-autobuilder/yocto-controller/controller.cfg
 /media/data/yocto-autobuilder/yocto-controller/buildbot.tac
 /media/data/yocto-autobuilder/yocto-worker/buildbot.tac

 Updating worker-init script used for google cloud building.

 If you wish to use your own generated username and password please
 modify the above files as needed. Please see the README for more
 information.

 Generating an .htpasswd file using your current username and (deleted, on
purpose) at /media/data/yocto-autobuilder/.htpasswd
#########################################################################

 Please modify /media/data/yocto-autobuilder/config/autobuilder.conf if you
wish to specify
 a different location in which to publish build artifacts, etc.

#########################################################################

 Ready to start the yocto autobuilder.

 The yocto-autobuilder runs buildbot 0.8.8 with some modifications and
 a different git fetcher (yoctogit.py)

#########################################################################
checking basedir
checking for running master
checking controller.cfg
LOADING CONFIG FILE
*error while parsing config file:*
Traceback (most recent call last):
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/Twisted-12.2.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py",
line 1187, in unwindGenerator
    return _inlineCallbacks(None, gen, Deferred())
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/Twisted-12.2.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py",
line 1045, in _inlineCallbacks
    result = g.send(result)
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/scripts/upgrade_master.py",
line 169, in upgradeMaster
    master_cfg = loadConfig(config, configFile)
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/scripts/upgrade_master.py",
line 53, in loadConfig
    config['basedir'], configFileName)
--- <exception caught here> ---
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/config.py",
line 149, in loadConfig
    exec f in localDict
  File "/media/data/yocto-autobuilder/yocto-controller/controller.cfg",
line 94, in <module>
    yocto_buildsets.createBuildsets()
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/autobuilder/Autobuilder.py",
line 65, in createBuildsets
    self.parseBuildSet(buildset)
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/autobuilder/Autobuilder.py",
line 102, in parseBuildSet
    self.parseRepos(buildset)
  File
"/media/data/yocto-autobuilder/lib/python2.7/site-packages/autobuilder/Autobuilder.py",
line 127, in parseRepos
    if layer.iterkeys().next() not in self.repos:
*exceptions.AttributeError: 'list' object has no attribute 'iterkeys'*
Errors loading configuration:
  error while parsing config file: 'list' object has no attribute
'iterkeys' (traceback in logfile)
 To start the autobuilder:
 ./yocto-start-autobuilder <worker|controller|both>

 To stop the autobuilder:
 ./yocto-stop-autobuilder <worker|controller|both>

>0< alain@esxi-ub1 Thu Mar 23 05:34 PM [master !?]
/media/data/yocto-autobuilder >

Any ideas on how to fix this?

On Mon, Nov 14, 2016 at 1:40 PM, Bill Randle <bill.randle@gmail.com> wrote:

> Yes, the 2 TB is for everything you might do with an AutoBuilder. The
> actual space used will be closer to your 35 GB, since you're building
> only a single image / work product. People have used BuilBot directly
> for automated builds, but using the AutoBuilder code (which runs
> BuildBot underneath) gives you added flexibility and capability
> without much additional overhead.
>
>     -Bill
>
> On Mon, Nov 14, 2016 at 8:13 AM, Alain Achkar <alain.achkar@triacta.com>
> wrote:
> > 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 <bill.randle@gmail.com>
> 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
> >> <pidge@toganlabs.com> 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
> >> > yocto@yoctoproject.org
> >> > 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
>



-- 

Alain Achkar, M.Eng. | Software Engineer

*Triacta Power Solutions*

(O) 613.256.2868 (C) 613.406.6520

*www.triacta.com  <http://www.triacta.com/>*

[-- Attachment #2: Type: text/html, Size: 18250 bytes --]

  reply	other threads:[~2017-03-23 21:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 17:35 Buildbot / Autobuilder / custom? Alain Achkar
2016-11-11 18:37 ` Beth 'pidge' Flanagan
2016-11-14 15:10   ` Bill Randle
2016-11-14 16:13     ` Alain Achkar
2016-11-14 18:40       ` Bill Randle
2017-03-23 21:40         ` Alain Achkar [this message]
2017-03-24 10:44           ` Joshua Lock
2017-03-24 16:05             ` Alain Achkar
     [not found]       ` <CABcw_OkUq_YX939GrV+SXFAcuKb4c+aHzKOK4Y5pOK+LTOMLWg@mail.gmail.com>
     [not found]         ` <CAGkf0HCOzd-_wPbCR9MREADq29vKFWK0jynqLYO5qMezi+txYw@mail.gmail.com>
2017-04-04  1:43           ` Alain Achkar
2017-04-21 15:39             ` Alain Achkar
2017-05-29 21:01               ` Alain Achkar
2017-05-31 16:21                 ` Joshua Lock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGkf0HCdi=Y00Aa=b=OqGVz0OL5N0cd4de6tK9CoDNv7P=Ee7A@mail.gmail.com' \
    --to=alain.achkar@triacta.com \
    --cc=joshua.g.lock@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.