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>
Our plugin is based on upstream buildbot's console plugin. Upstream moved
away from coffescript and made a number of other fixes and improvements.
Run decaffeinate on the coffeescript to translate to angularjs and then
convert to the new build environment and standards.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It seems the previous approach was confusing buildbot about the task status
so try and be more specific and use better APIs to avoid this.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We already have a log, don't duplicate the data as a property as it will
cause excess database growth.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For new tasks, hide errors/warnings if not present, don't monitor steyXY
logfiles as they're no longer needed and ensure description is provided
by our code as shellCommand doesn't handle it.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rather than running all the work in a single run-config command, split this into
multiple steps. This allows for separate result code reporting, timestamps
for indvidual steps and is generally much cleaner. The naming and so on will need
further work but this is a start.
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>
Since clobber is crossing two file systems in this case the worker
can delete the files faster than it can move them
Also fixes a occasional race that results in build failures
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some instructions on setting up the hash equivalency server for
an autobuilder instance that operates independently of the Yocto one.
This all still assumes that the user is planning on running the controller,
worker, and janitor on the same build host, although the hash equivalency
server itself doesn't need to be.
Also made some minor changes to the list of packages to install to support
the autobuilder on Ubuntu, since there were some typos in the package names.
Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
