From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 696FCE00BAB; Mon, 3 Apr 2017 18:44:07 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.218.44 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [209.85.218.44 listed in dnsbl.sorbs.net] Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 36BCDE00B76 for ; Mon, 3 Apr 2017 18:44:03 -0700 (PDT) Received: by mail-oi0-f44.google.com with SMTP id r203so147280775oib.3 for ; Mon, 03 Apr 2017 18:44:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=triacta.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=uUTUTQnJ8zS/l8ngwn+DfuEJ00h+2i8IJUIfe7xxADg=; b=NwXsh9hV7st5c+EL9n9H4wloBCc3VICfjx7mVnaAihxb5/itGzREKQ0OIrcH1UxxES Oej37Y4Q0vISqiA1lIte1ikHzRs9aRxIIvpmox4XlUMc09kkG1/OBJU0arkHXZkj2vlR i95TVbqSTRE5JZiU5UoyF9ZWq3J/Ts5x4/KJs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=uUTUTQnJ8zS/l8ngwn+DfuEJ00h+2i8IJUIfe7xxADg=; b=nyOaA5qfsaf4o+brDJxAwU60xARZmjf3yh4t5i+8tkg9QU4+4u0rfYZB/6eOjIUVB8 cPgAlHw/kIMpq5wH1b9cGJ2mQhaISGPwiGemBU/863F8OX84TiLvLHYEgXF2rFolQvPf 0XcbUGFdSRvcDTK+JGUMrpVVeEwbU2bADUWxXvnXDQ83M3Pc3YRZRIkvfDLKp8Z95KFn xswfO3UC1TAaeZULxRQqLny2e1WCdB/Y/EdHjQWP2eoKSslyPyZGWkoerOjkhPHLxyFi W7CNjyNvJ8SLzVHAcbExBvOlDw+VXrF8assEzUMC3Vw8Fv7DQrOCyPk2h2X/2VMajzTk oMiA== X-Gm-Message-State: AFeK/H06i/7BbCPgymJTR8R69vViSztqim3sheUIeQI4gFPk9TB09aflVIx7KPxdN5nHzjFRetdsE4MSwjWVZiYM X-Received: by 10.202.79.13 with SMTP id d13mr10672045oib.1.1491270242536; Mon, 03 Apr 2017 18:44:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.4.45 with HTTP; Mon, 3 Apr 2017 18:43:22 -0700 (PDT) In-Reply-To: References: <1478889473.18810.3.camel@toganlabs.com> From: Alain Achkar Date: Mon, 3 Apr 2017 21:43:22 -0400 Message-ID: To: Chris Whittenburg , yocto@yoctoproject.org Subject: Re: Buildbot / Autobuilder / custom? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Apr 2017 01:44:07 -0000 Content-Type: multipart/alternative; boundary=001a113d809812241f054c4d699f --001a113d809812241f054c4d699f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Chris! I had to put this task on hold and I am re-visiting it now. I followed the instructions here: http://git.yoctoproject.org/cgit.cgi/ yocto-autobuilder/tree/README-QUICKSTART and managed to force one of the builds that comes with Yocto. I got errors but I'm not interested in the Yocto-provided nightly builds anyway. (The errors are related to buildhistory - it seems that some builds set Buildhistory=3DTrue but I haven't set up a git repo for build history) Now, I am still confused how to build the Variscite image for the i.MX6UL. We are still at Jethro but don't mind upgrading to Krogoth. I would appreciate some general guidelines on how to take the instructions in here: http://variwiki.com/index.php?title=3DDART-6UL_Yocto_Jethro_R1_build and transform them to the config format that Autobuilder understands. Mainly, I understand that I have to: 1) checkout the source code $ mkdir ~/var-mx6ul-mx7-yocto-jethro $ cd ~/var-mx6ul-mx7-yocto-jethro $ repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1.15-1.0.0_ga $ repo sync $ cd ~/var-mx6ul-mx7-yocto-jethro/sources $ git clone https://github.com/varigit/meta-variscite-mx6ul-mx7.git -b imx_4.1.15_ga-var01 2) copy and patch $ cp meta-variscite-mx6ul-mx7/scripts/var-setup-release.sh ../ $ patch -p1 < meta-variscite-mx6ul-mx7/patch/Fix-FSL-multi-patch-append-bug= s.patch 3) setup a download directory $ sudo mkdir /opt/yocto_downloads $ sudo chmod 777 /opt/yocto_downloads/ $ sed -i 's/DL_DIR ?=3D "${BSPDIR}\/downloads/DL_DIR =3D "\/opt\/yocto_downloads/g' conf/local.conf 4) setup the environment $ cd ~/var-mx6ul-mx7-yocto-jethro $ MACHINE=3Dimx6ul-var-dart DISTRO=3Dfsl-imx-x11 source var-setup-release.sh -b build_x11 5) build $ bitbake fsl-image-gui I looked at some nightly-*.conf files, for example nightly-x86-64.conf to try to guess what to do. I know I have to create a file like nightly-var-mx6ul.conf but given that Variscite is not using the 'repo' command that Freescale is using (they do a git clone) and given step (2) of copying their own setup script and patching the whole freescale meta- layers, I am not sure about what to put instead of the line: {'CheckOutLayers': {}}, I also can't figure out how the info in Variscite's build-x11/local.conf can be translated to the Autobuilder format, i.e. where to specify all these config parameters. Any help would be greatly appreciated. On Mon, Nov 14, 2016 at 12:35 PM, Alain Achkar wrote: > Thanks Chris! > > This is the answer I was looking for. > > On Mon, Nov 14, 2016 at 11:58 AM, Chris Whittenburg > wrote: > >> >> Hi Alain, >> >> We use the same module-- Variscite DART MX6, and I was able to hack the >> yocto autobuilder to build our image nightly. I host it all on a single >> machine. >> >> -chris >> >> >> On Mon, Nov 14, 2016 at 10:13 AM, Alain Achkar >> wrote: >> >>> Thanks for your answers! From reading these links, it is still not clea= r >>> to me if this might be overkill for my requirements. AB Cluster Setup t= alks >>> 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 runnin= g >>> one build for one machine type (the Variscite DART-6UL i.MX6UL arm-base= d >>> 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 i= n >>> parentheses) but my question remains: do I only install BuildBot and tr= y to >>> build my machine type with it, or do I install Autobuilder? >>> >>> On Mon, Nov 14, 2016 at 10:10 AM, Bill Randle >>> 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 >>>> 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=3DD >>>> >> 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=C3=A1n Labs >>>> > www.toganlabs.com >>>> > >>>> >> >>>> >> What is the faster path to get up and running? >>>> >> >>>> >> Thanks! >>>> >> Alain. >>>> >> >>>> >>> >>> --001a113d809812241f054c4d699f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Chris!

I had to put this task on hol= d and I am re-visiting it now. I followed the instructions here:=C2=A0=C2=A0http://git.yoctoproject.org/cgit.cgi/yo= cto-autobuilder/tree/README-QUICKSTART=C2=A0and managed to force o= ne of the builds that comes with Yocto. I got errors but I'm not intere= sted in the Yocto-provided nightly builds anyway. (The errors are related t= o buildhistory - it seems that some builds set Buildhistory=3DTrue but I ha= ven't set up a git repo for build history)

Now= , I am still confused how to build the Variscite image for the i.MX6UL. We = are still at Jethro but don't mind upgrading to Krogoth.

=
I would appreciate some general guidelines on how to take the in= structions in here:
and transform them to the c= onfig format that Autobuilder understands.

Mainly,= I understand that I have to:

1) checkout the sour= ce code
$ mkdir ~/var-mx6ul-mx7-yocto-jethro
$ cd ~/var-mx6ul-mx7-yocto-jethro
$ repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1.15-1.0.=
0_ga
$ repo sync
$ cd ~/var-mx6ul-mx7-yocto-jethro/sources
$ git clone https://github.com/varigit/meta-variscite-mx6ul-mx7.git -b imx_4.1=
.15_ga-var01

2) copy and patch
$ cp meta-variscite-mx6ul-mx7/scripts/var-setup-release.sh =
../
$ patch -p1 < meta-variscite-mx6ul-mx7/patch/Fix-FSL-multi-patch-append-=
bugs.patch

3) setup a download direct= ory
$ sudo mkdir /opt/yocto_downloads
$ sudo chmod 777 /opt/yocto_downloads/
$ sed -i 's/DL_DIR=C2=A0?=3D "${BSPDIR}\/downloads/DL_DIR =3D &quo=
t;\/opt\/yocto_downloads/g' conf/local.conf

<= div>4) setup the environment
$ cd ~/var-mx6ul-mx7-yocto-jethr=
o
$ MACHINE=3Dimx6ul-var-dart DISTRO=3Dfsl-imx-x11 source var-setup-release.s=
h -b build_x11

5) build
$=
 bitbake fsl-image-gui

I looked at som= e nightly-*.conf files, for example nightly-x86-64.conf to try to guess wha= t to do.

I know I have to create a file like night= ly-var-mx6ul.conf but given that Variscite is not using the 'repo' = command that Freescale is using (they do a git clone) and given step (2) of= copying their own setup script and patching the whole freescale meta- laye= rs, I am not sure about what to put instead of the line:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 {= 9;CheckOutLayers': {}},
=C2=A0

I also can't figure out how the info in Variscite's build-x11/loc= al.conf can be translated to the Autobuilder format, i.e. where to specify = all these config parameters.

Any help would be gre= atly appreciated.


On Mon, Nov 14, 2016 at 12:35 PM, Alain Achkar <alain.achkar@triacta.com> wrote:
Thanks Chris!

This is the answer I was looking for.

On Mon, Nov 14, 2016 at 11:58 AM, Chris Whittenburg <whitte= nburg@gmail.com> wrote:

Hi Alain,

We use the same module-- Variscite DART MX6, and I was able to hack the y= octo autobuilder to build our image nightly.=C2=A0 I host it all on a singl= e machine.

-chris


On Mon, Nov 14, 2016 at 10:13 AM, Alain Achkar <alain.a= chkar@triacta.com> wrote:
Thanks for your answers! From reading th= ese links, it is still not clear to me if this might be overkill for my req= uirements. 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 loca= l sstate mirror are included, additional worker space is required."= ;

Currently, my build only takes 35GB, so I th= ink what these links are talking about is how to replicate what the Autobui= lder project=C2=A0https://autobuilder.yoctoproject.org/ already = does.

To clarify, I am not intere= sted in running builds and tests for everything that Yocto already builds a= nd tests (i.e. all the processor architectures, all the machine types, etc.= ).=C2=A0 I am interested in running one build for one machine type (the Var= iscite DART-6UL i.MX6UL arm-based processor, for which NXP/Freescale and Va= riscite have provided recipes and layers for).

I know that autobuilder includes BuildBot (this is why I specified i= t in parentheses) but my question remains: do I only install BuildBot and t= ry 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:
=C2=A0 =C2=A0 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.

=C2=A0 =C2=A0 -Bill

On Fri, Nov 11, 2016 at 10:37 AM, Beth 'pidge' Flanagan
<pidge@toganlab= s.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 i= s
>> based on Freescale/NXP i.MX6UL (http://variwiki.com/= index.php?title=3DD
>> ART-6UL_Yocto_Jethro_R1_build).
>>
>> Currently, developers run builds manually on their desktops. We ar= e
>> considering using a continuous integration server. I found out tha= t
>> The Yocto Project uses Autobuilder which in turn uses BuildBot. I<= br> >> 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=C3=A1n Labs
> www.toganlabs.com
>
>>
>> What is the faster path to get up and running?
>>
>> Thanks!
>> Alain.
>>

--001a113d809812241f054c4d699f--