From: Beth 'pidge' Flanagan <pidge@toganlabs.com>
To: Alain Achkar <alain.achkar@triacta.com>, joshua.g.lock@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: Buildbot / Autobuilder / custom?
Date: Fri, 11 Nov 2016 18:37:53 +0000 [thread overview]
Message-ID: <1478889473.18810.3.camel@toganlabs.com> (raw)
In-Reply-To: <CAGkf0HCnrCpufRV9U_pz7LYDkCvhK7of_1=0zgS425GeGYSUPQ@mail.gmail.com>
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
next prev parent reply other threads:[~2016-11-11 18:38 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 [this message]
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
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=1478889473.18810.3.camel@toganlabs.com \
--to=pidge@toganlabs.com \
--cc=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.