QA report app is merged with the lavaphabbridge app and
it is now being served on qa.apertis.org. So update the
test-cases-url and bridge-url to point to qa.apertis.org.

We now need to also (keep lavaphabbridge.apertis.org as is for now) serve the same app under qa.apertis.org
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Continuing with the fix in ddd20ee7

 apply the same approach in Dockerfile.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Test execution type is added to test report and test
results are highlighted. So regenerate the screenshots.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

A column with test execution type is added to
indicate whether it is an automated or manual test.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Improve the way counters are rendered by adding
colors to make it easier to spot issues.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

_lookup_app_object is removed in Flask version 2.2.0.
Due to this flask-dance 6.0.0 is incompatable with Flask >=2.2.0.
So this results in below error when Flask 2.1.3 is used,

ImportError: cannot import name '_lookup_app_object' from 'flask.globals'

https://github.com/singingwolfboy/flask-dance/issues/396
https://github.com/pallets/flask/commit/0b2f809f9b56861dae3ae5154d73b4afaf632a0a



So pin Flask to version 2.1.3 to fix this error.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Walter Lozano authored Aug 01, 2022 and Ryan Gonzalez committed Aug 01, 2022

Update LAVA URL after new deployment with kubernetes.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Fix the rendering of the affected image versions by using bullets,
allowing to have one link per line.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Since warranty information is being handled in management data section
only in Phabricator remove it from the task template.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

These are now on the linked section of the website instead.

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Previously, the list of releases shown on the index page, for the
purpose of seeing the test cases defined within, was hardcoded. Now,
instead, it's dynamically pulled from the test cases repository, with
some magic applied on top to only show relevant releases, as the
hardcoded list did.

In order to avoid thus having to change the test case screenshots every
time a new release is branched, the test cases filter out releases newer
than the rough range that the test data was taken from.

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

All the places were platforms were hardcoded w/ related logic have been
generalized to using values from a configuration file.

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

In order to keep all the configuration in one place, this also moves Git
repository cloning into being handled by the app itself, instead of
being done in the Dockerfile.

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

It will be possible to disable bug tracking via configuration, so it is
no longer particularly useful to remove this in the future.

(The incorrect flag description is also fixed.)

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Internal platforms are specified as `ARCH-internal`, but the previous
code would leave the `-internal` suffix on. This would result in the
resulting glob looking a bit like `...ARCH-internal-*-internal`, i.e. it
has a double `-internal`, which isn't correct.
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Otherwise, it fails to validate our certificates:
https://phabricator.apertis.org/T8535

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Including the database results in larger images and, more annoyingly,
longer build times, as the entire database needs to be sent to the
Docker daemon as part of the build context.

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

For development purposes, just disabling SELinux isn't a huge deal and
avoids the need to disable SELinux enforcing system-wide in order to run
qa-report-app.

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Without this, attempting to access the volume contents results in
"Permission denied" errors.

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Before it was a mix of tabs and spaces, with a tab width of 8 but an
indentation size of 2(??).

https://phabricator.apertis.org/T8854

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

To append new comments in to same test-case failure the application checks
for open issues with the test-failure label. However, by default only the
last 20 are returned.

In order to properly find an open test-case failure in Gitlab issues,
retrieve all the open issues.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Existing links to testcase definitions are broken after
migration to QA report app.

The below links yield 404 not found. This is because the
routes for the testcase definitions are under `testcases/`.
<release>/<testcase>.html
latest/<testcase>.html
<testcase>.html

Fix the broken links by,
<release>/<testcase>.html will 308 permanent redirect to testcases/<release>/<testcase>.html
latest/<testcase>.html will 307 temporary redirect to testcases/<default_branch>/<testcase>.html
<testcase>.html will 307 temporary redirect to testcases/<default_branch>/<testcase>.html
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

In commit af3b4035 several changes were introduced, which does not seem
desirable.

First, results for not supported releases are not shown any more, which has
no clear goal. Let's keep this references for historical reasons since we
also keep the release information in the website.

Also, the sort order of reports was changed to be based on the release they
belong, starting with the newest release. This change breaks the previous
order which was based on the latest results available. Since it is more
useful have the list sorted based on the latest results as it reflects the
current states of all the available releases revert that specific change.

Keep the new release list and its order since it looks more natural.

Since configuration is deployed using chef cookbooks add a mention in the
readme file.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

By mistake a duplicate default config entry was left, causing login to fail
if the proper configuration option was not supplied. Fix the issue by
removing the wrong default.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Test suites and reports list page is updated.
So regenerate the index page.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

When the test case ID is clicked in test report page,
it redirects to https://qa.apertis.org/ which is hard-coded
in 'test-cases-url'. Instead it needs to redirect
to the correct release test case page.

Modify 'test-case-url' to point to https://lavaphabbridge.apertis.org


and create the url for test case page and pass to render_template.
Fix the url path in submit_report.html to render the correct test cases.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

v2019/v2020 releases are no longer supported.
So do not show the test suites and reports for
the not supported releases.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

The test case index page does not mention the suite
name and it needs to checked from the url. Add the
suite version in the header for the individual test
case index pages.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

When rendering the test case page, the test case table object was
created each time to access the methods which fetches test case data.
The object initilization takes time since it creates the test cases
table, data and images from the bare git repository.

Instead use the test case table object which is already created
to access the test case table. This fixes the slow rendering of
test case pages.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Since testcase definition rendering is integarted to qa-report-app,
regenerate the index-page screenshot for the tests to pass.
Add tests to check rendering of test cases which has images.

- Fetch the testcase data from the bare git repository.
- Port atc_renderer code from apertis-test-cases
  and adapt to render data fetched from the bare git repository.
- Reworked qa-report-app homepage to also link to the per-branch testcase definitions.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

After adding support for Gitlab issues, a bug was introduced by using
a wrong function to connect to bug tracking system. Fix the problem
by calling the correct functions.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

With new git version additional checks are done to confirm if a repository
is safe. One of such checks is the ownership of the files, which triggers
an error by default. Since QA Report App runs some tests with testuser
this check does no pass causing the pipeline to fail.

Workaround this issue by cloning the repository with the testuser.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>