Build caption is set to oe-core build branch by yocto-autobuilder-helper
scripts. Today we are using this caption to describe all branches on the
console view, but some repos might use other branches.
Explicitly use oe-core and bitbake branch names instead.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some errors were observed on the console view when the URL string is
undefined. Just mask URLs in such case, as it would otherwise lead to a
JS exception.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of always looking for commits in main repos, use values provided
int the "repo_*" build properties. Make sure to use https protocol.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This might need to be updated once https://errors.yoctoproject.org is
fixed for the bitbake-setup switch.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix an issue where the browser pop-up label was the same for all build
of a builders group.
Fixes [YOCTO #15911]
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When using selectors, all fields modified by the selector will be
successively focused, inducing a potential page scroll. Save current
scroll before applying the release selector and set back this scroll
once the selector has been applied, setting back the page at the same
position.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Compact a bit the force build window, to look like what we had on
buildbot 3.8.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The yp_build_revision property disappears from the build instance once
the build is done. There is no reason for its value to change, so keep
the last seen value in revision mapping. This will prevent finished
builds to jump back to "Unresolved Revision".
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Builds from similar builders have to be in the same <td>, compacting a
bit the whole view.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Plugin changed a lot with the buildbot transition from angularjs to
reactjs: start our own plugin customisation from scratch.
This commit only copies sources from buildboot git, without any
modification.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
This was changed compared to the upstream console view code due to bugs in our
own changes code. Those are now fixed so revert to the upstream version allowing
these data structures to persist and not always be reset.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Where we inject a "fake" change, we then never update the list of builders it
contains. This leads to bugs in the UI rendering since the builders list
might not be the accurate in early calls to the onChange function.
Keep track of fake changes and update those too so the builders list
is maintained.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If a field doesn't exist in the current build, allow the selector to still work
(e.g. meta-arm branch in a-quick).
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>
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>
The previous approach was basically repeatedly adding change nofification
calls recursively which could lock up the browser. It turns out nofitications
are not being generated properly in upstream buildbot.
https://github.com/buildbot/buildbot/issues/4321https://github.com/buildbot/buildbot/pull/4323
For now accept a UI regression which will get fixed when the above is
fixed. Avoid the current performance problems.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
