[Toaster] [PATCH 09/10] toaster-manual: update runbuilds instructions

[Brian Avery]

Hi,

I was trying out your instructions/production setup on an ubuntu
16.04/mysql setup and got the following error:
$>TOASTER_DIR=`pwd` TOASTER_CONF=./meta-poky/conf/toasterconf.json
./bitbake/lib/toaster/manage.py checksettings --traceback 2>&1 | tee
mychecksettings.log

resulted in

django.db.utils.DataError: (1406, "Data too long for column 'license' at row 1")

I'm attaching the logfile.

Have any of you seen this before? It kinda stops me cold here. Sadly,
the error doesn't let me know what table or data was too long.

-b
an intel employee

p.s. other issues I've seen so far
1) 3.7.2.1
sudo mkdir /var/www/toaster
need a : sudo chown toaster /var/www/toaster
2) 3.7.2.4
SECRET_KEY needs a pointer to the Django documentation so people know
what it is:
https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SECRET_KEY

3) 3.7.2.6
the TOASTER_DIR=... checksettings line is too long and got truncated
for me when my pdf was made.  We should probably break it in 2 or use
exports.






On Fri, Jul 8, 2016 at 6:30 AM, Michael Wood <michael.g.wood at intel.com> wrote:
> Pasting this in as it's an updated version of this patch:
>
>
> commit 74e368b1855bbf4321f73b09a0f2c973b1e33c61
> Author: Ed Bartosh <ed.bartosh at linux.intel.com>
> Date:   Mon Jun 27 17:37:40 2016 +0300
>
>     toaster-manual: update runbuilds instructions
>
>     Added sample configuration files and instructions for the runbuilds
>     systemd service. Service runs runbuilds in a screen session for user
>     convenience. User can attach to the session to see the runbuilds output,
>     monitor logs and build environment.
>
>     Signed-off-by: Ed Bartosh <ed.bartosh at linux.intel.com>
>
> diff --git a/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> b/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> index febbd15..26e71c8 100644
> --- a/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> +++ b/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> @@ -438,22 +438,49 @@
>                        </literallayout>
>                        </para></listitem>
>                    <listitem><para>
> -                      Install the build runner service.
> -                      This service needs to be running in order to dispatch
> -                      builds.
> -                      Use this command:
> +                      Prepare systemd service to run toaster builds.
> +                      Here is a sample configuration file for the service:
>                        <literallayout class='monospaced'>
> -   /var/www/toaster/poky/bitbake/lib/toaster/manage.py runbuilds
> +   [Unit]
> +   Description=Toaster runbuilds
> +
> +   [Service]
> +   Type=forking
> +   User=toaster
> +   ExecStart=/usr/bin/screen -d -m -S runbuilds
> /var/www/toaster/poky/bitbake/lib/toaster/runbuilds-service.sh start
> +   ExecStop=/usr/bin/screen -S runbuilds -X quit
> +   WorkingDirectory=/var/www/toaster/poky
> +
>
>
> This is kind of interesting from a developer of Toaster point of view but I
> don't think we should be recommending screen in the production setup.
> Toaster should be logging all the useful output anyway.
>
>
>
> +   [Install]
> +   WantedBy=multi-user.target
>                        </literallayout>
> -                      Here is an example:
> +                      And the runbuilds-service.sh script that you should
> put into /var/www/toaster/poky/bitbake/lib/toaster/ and
> +                      set executable permissions to it.
>                        <literallayout class='monospaced'>
> -   #!/bin/sh
> -   # toaster run builds dispatcher
> -   cd /var/www/toaster/
> -   source ./venv/bin/activate
> -   ./bitbake/lib/toaster/manage.py runbuilds
> +   #!/bin/bash
> +
> +   #export http_proxy=http://proxy.host.com:8080
> +   #export https_proxy=http://proxy.host.com:8080
> +   #export GIT_PROXY_COMMAND=$HOME/bin/gitproxy
> +
> +   cd ~/poky/
> +   source ./oe-init-build-env build
> +   source ../bitbake/bin/toaster $1 noweb
> +   [ "$1" == 'start' ] && /bin/bash
>                        </literallayout>
> -                      </para></listitem>
> +                  </para></listitem>
> +                  <listitem><para>
> +                      Run the service:
> +                      <literallayout class='monospaced'>
> +   # service runbuilds start
> +                      </literallayout>
> +                      As service is running in a detached screen session
> you can attach to it using this command:
> +                      <literallayout class='monospaced'>
> +   $ sudo su - toaster
> +   $ screen -rS runbuilds
> +                      </literallayout>
> +                      And detach from it again using 'Ctrl-a' followed by
> 'd' key combination.
> +                  </para></listitem>
>                </orderedlist>
>                You can now open up a browser and start using Toaster.
>            </para>
>
>
> --
> _______________________________________________
> toaster mailing list
> toaster at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/toaster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mychecksettings.log
Type: application/octet-stream
Size: 5925 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20160711/9e98d8a9/attachment.obj>