We need to show the build-appliance configuration on nightly as well as
nightly-build-appliance.
Also, default to AUTOREV, matching the behaviour of the old codebase.
Drop the "DEFAULT" magic value, default to that if a revision isn't specified.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Finish the porting work started by Joshua Lock, accounting for changes
in buildbot APIs/data model and changes from py3, particular around
character encoding.
This also changes the behaviour of the plugin slightly. We now
use the build URL in the header to match builds. With the new codebase
we can walk the parent tree of triggers builds to ensure we always have
the correct parent build url. This means we can drop a lot of the older
more imprecise build matching logic.
Also simplify the format in the wiki log to one output format which lists
all step failures for each build, even in the parent case.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default, since the yocto-autobuilder-helper repository is the only
one that buildbot actually checks out in a step, the revision of that is
the one that gets associated with the build; however, it's much more
useful to have the revision set to the poky revision, so add a step that
does that.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Based on the SetDest step in the old codebase this function is used to
determine where the artefacts of a build should be published. In order to
avoid overwriting previously published content the function keeps a list of
destinations which have already been created and written to on the
controller and avoids reusing them.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Uses the values submitted to the scheduler to determtine the major number
of the release for the purposes of publishing per-major release
shared-state artefacts.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Removing the build directory (with rm -fr) can take a significant amount
of time, longer than the standard buildbot timeout, which delays the
builds. Instead, we use the clobberdir script from the helper repository.
This script moves the directory contents out of the way to a location which
is reaped by a background process.
Unfortunately this assumes/requires a copy of the repository is kept in the
home directory of the user running buildbot.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Initial prototype of using yocto-autobuilder-helper scripts from vanilla
buildbot to replicate yocto-autobuilder configuration.
* README.md is updated to describe goals and approach
* TODO contains known issues and work items, TODO: comments in the code
point to specific locations of work
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
