fedora-ci/ciboard

ciboard's Issues

have a REJECT button in gating

Hi,
if we see a gating fail (or any other serious fail here and there) we should be able to mark the build as broken (rejected). Otherwise, devel might be unsure if the build was already inspected and just not waived.

In addition, we would see a ratio of failing gating tests that were rejected or waived, which is in my opinion useful as well.

Misleading gating status for runing tests

When I see something like this in the list of results on OSCI Dashboard:

it seems to me that there are 4 errors I have to take a look at and solve. But in fact, these four "errors" are just running tests and I have to wait.

Would it be possible to somehow represent that the tests are not yet done differently? It'd also be great to have a different icon in the title of the page so I can use an automatic refresh and see from the title of the browser tab whether there is something to do or not yet.

Please update Node.js to supported version - Node 12 LTS is EoL

Support of Node 12 LTS ended on 30 Apr 2022

Currently supported LTS versions:

• Node 14 LTS - supported till 30 Apr 2023
• Node 16 LTS - supported till 11 Sep 2023
• Node 18 LTS - supported till 30 Apr 2025

Webpack >= 5 no longer include polyfills for node.js core modules by default.

Module not found: Error: Can't resolve 'stream' in '/home/runner/work/ciboard/ciboard/node_modules/sax/lib'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
	- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "stream": false }

Possible solution: Install polyfills and resolve them or turn them off using new Webpack API

Blocks: #6

Errata automation tab would deserve a visual notification

The new Errata Automation tab is great but I believe it would require some sort of visual notification in case there are errors present.