Broke the document up into more sections, and added some info
to make it clear that the same instructions for setting up
the systemd autobuilder can be used to start it manually.
Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To quote the manual, "The branch on which the change occurred.
Note that ‘trunk’ or ‘master’ is often denoted by None."
so lets add None as well and hope master builds appear properly.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For some reason the older syntax for specifying the branch isn't working. Use
the newer one instead which does.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new target to run layer checks every 24 hours on various layers we don't
test as part of the standard test runs.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also tweak hardknott to build meta-arm master as there is no hardknott branch
yet.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The instructions in README-Guide.md are a good starting point, but there
are some additional guidelines in this patch for setting up worker nodes
which may be useful to others who want to run their own Autobuilder
instance. Specifically, it adds:
- Section 1.3 on adding additional worker nodes to a cluster
- Section 1.4 on setting up an NFS share for the controller and workers
to reference
- A link to the Yocto Manual where the requirements to support running
builds on Ubuntu/Debian systems is listed
- A note to make sure that any new users (pokybuild3) created for the
Autobuilder have LANG set in their bash profile
Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This adds meta-agl-core as target.
Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The log boolean variable conflicted with log.err() calls, fix this
and avoid tracebacks.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For reasons unknown, logs may not always be reported, handle this
more gracefully so the error is still logged.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We were pushing duplicate builder values into changes list which was causing
angular to get rather upset, triggering console warnings and heavy CPU usage.
Stop doing that. Also drop the pointless return value.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The logic in the function was odd, we need to trigger onChange if we update
any values. The return values are also pointless. Fix and clean up the code
logic accordingly.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
