The log boolean variable conflicted with log.err() calls, fix this
and avoid tracebacks.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Preseve a footer 'Archived Logs' section at the end of the BuildLog wiki
page. This will be later used for archiving purposes.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We want the wiki log to primarily contain full and quick builds for
processing by SWAT. The buildperf log entries are distracting but
in case of failure we do need them there so adjust the code to handle
this.
Also, don't log reports of skipped builds but do log build warnings, since
we do want warnings to be acted upon now.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Buildbot would hang for several minutes when cancelling builds. We need to defer
this work (which involved network calls) to a thread so that the reactor isn't
blocked.
Use a lock to ensure we only update the wiki one entry at a time.
Also tweak the logging to allow easier debugging (include the parent build ID)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This ensures one entry is shown per step with the logs on the same line. The logs
are shown with the log names and the step name is only shown once. This make
the resulting wiki entry much easier to use.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When a wiki page is empty, or only contains a single entry, ensure
the code still works and use empty content to initialise it.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Entries were getting added even in the success case, fix this.
Also only update the wiki if the data changes.
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>
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>
