Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

No need to run the gitlab-rulez diff because the dashboard already
reports issues.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

These branches are not used anymore, so no need to retrieve data
about them. This will reduce the size of the cache file.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Parsing the big cache file can sometimes lead to an OOM issue with
packaging-data-fetch-downstream. This option allows to disable the
cache at this step to unblock dashboard updates.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

In case of wrong settings detected, gitlab-rulez returns a non
0 value and it makes the job marked as failed. So, this case can
be ignored. But gitlab-rulez running in `apply` mode should not
fail.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This objet is used to compare default settings with current
settings of packages.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Git repositories settings are set by gitlab-rulez.
If a setting is wrongly set a an error is displayed on the
dashboard.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

A button is added on the dashboard next to the "Update all" button,
to run the trigger-gitlab-rulez job using the "apply" mode.
This allows developers to easily fix "pkg/*" repositories settings.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

In case of wrong gitlab repositories settings an easy way to fix
them should be available. This job fixes all "pkg/*" repositories
settings by running gitlab-rulez. By default, it only reports what
the rules would do. Setting the TRIGGER_GITLAB_RULEZ to "apply"
will apply the rules.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

`apertis/*`, `debian/*` and `pristine-lfs` should be protected.
If these branches are not protected an error is displayed on the
dashboard.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

The gitlab default branch should match the latest Apertis release
providing the package. This check verifies if the default branch
corresponds to the latest Apertis release based on the published
package. If there is a mismatch, an error is displayed on the
dashboard.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Severity of security updates are changed to error.
Added a ftbfs domain for package build failures.
This allows filtering the dashboard report for OBS
package build error and security updates easily.

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

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Due to badly formatted tag the detection of updates in the dashboard was
broken. The version in debian/bullseye was higher than the one actually
in bullseye. This prevented the dashboard from reporting about pending
updates. This commit reports error when the version in debian/buster or
debian/bullseye is higher than the one in upstream buster/bullseye.

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

Emanuele Aina authored 2 years ago and Vignesh Raman committed 2 years ago

The python-gitlab package started warning about some ambiguous usage of
their API:

    UserWarning: Calling a `list()` method without specifying `all=True`
    or `as_list=False` will return a maximum of 1 items. Your query
    returned 1 of 3 items. See
    https://python-gitlab.readthedocs.io/en/v3.5.0/api-usage.html#pagination


    for more details. If this was done intentionally, then this warning
    can be supressed by adding the argument `all=False` to the `list()` call.
    (python-gitlab: /usr/lib/python3/dist-packages/gitlab/client.py:879)

We actually do that on purpose to only get the latest pipeline for each
branch, so add `all=False`.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Avoid overusing single-letter variable names with large scopes, use
longer names to better convey their purpuse.

Purely cosmetic, this should not introduce any behavioral change.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

We are already storing artifacts for successful runs. We should also
store the artifacts for the failing jobs, for debug logs.

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Expand the list of packages that had to be renamed on GitLab because
their name contains characters that are not valid for project names.

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

Ignore debian/buster* pipelines failure for the linux package,
since the one tracking debian/buster was v2019.

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

All the development happens on v2023dev3 and mirroring
on the Apertispro side is complete for v2023dev1 and
v2023dev2. So we can stop monitoring v2023dev1 and v2023dev2.

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

Separate the component for v2023 as we do not have hmi any more.

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

aptly seems to export its Release files with padding between columns to
align them, e.g.:

```
03dbf158875ca31ec49be21ce8f8b5b0 13453697 development/binary-amd64/Packages
142723c7e10f049964bb791ff4458fe9  3961225 development/binary-amd64/Packages.gz
e5901baeb150db5d020a5e3bcd87d166      174 development/binary-amd64/Release
```

instead of the previous:

```
03dbf158875ca31ec49be21ce8f8b5b0 13453697 development/binary-amd64/Packages
142723c7e10f049964bb791ff4458fe9 3961225 development/binary-amd64/Packages.gz
e5901baeb150db5d020a5e3bcd87d166 174 development/binary-amd64/Release
```

This broke parsing the files, since it would previously split by a
single space, resulting in several "columns" that were entirely empty.

https://phabricator.apertis.org/T9101



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

Ritesh Raj Sarraf authored 2 years ago and Vignesh Raman committed 2 years ago

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Ritesh Raj Sarraf authored 2 years ago and Vignesh Raman committed 2 years ago

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Ritesh Raj Sarraf authored 2 years ago and Vignesh Raman committed 2 years ago

If the option is chosen, log to a file instead.

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Emanuele Aina authored 2 years ago and Vignesh Raman committed 2 years ago

In some cases the dashboard generated links to trigger new pipelines
with an empty ref because it was using a non-existing `name` property
on the branch in the report, which is just a string.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Errors such as authentication failures are still problems on our end
that retrying will not solve.

https://phabricator.apertis.org/T8543



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

The HTML being scraped isn't exactly the same, so loosen the selectors
a bit.

https://phabricator.apertis.org/T8543



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

For some strange reason, omitting the trailing slash here results in
the access being denied. Doing so with curl works correctly, but curl
does seem to redirect the URL to contain the trailing slash anyway...
It's not clear whether this is an issue somewhere in reqwests-land or
elsewhere, but for the moment, this "fix" should do.

https://phabricator.apertis.org/T8543



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

https://phabricator.apertis.org/T8543



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

https://phabricator.apertis.org/T8543



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

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

LICENSING_REPORT_MISSING: no `apertis/debian/copyright` found -> warn
LICENSING_OVERRIDE: `override-license:` is found in `apertis/debian/copyright.yml` -> warn
LICENSING_GLOBAL_WHITELIST: `*` is found in `apertis/debian/copyright.whitelist` -> notice
LICENSING_GLOBAL_DEFAULT: `.*`: is found in `apertis/debian/copyright.yml` -> notice (unless unfriendly - dual or not)
LICENSING_GLOBAL_DEFAULT_UNFRIENDLY: global default found, not dual but unfriendly -> warn
LICENSING_GLOBAL_DEFAULT_DUAL_UNFRIENDLY: global default found, set to dual and at least one of them is unfriendly -> warn

Signed-off-by: Andre Moreira Magalhaes <andre.magalhaes@collabora.com>

Signed-off-by: Andre Moreira Magalhaes <andre.magalhaes@collabora.com>

For this initial version domains are derived from the `Report`
enum name but this change should add more flexibility for future
improvements/categorization.

Signed-off-by: Andre Moreira Magalhaes <andre.magalhaes@collabora.com>

- license report missing -> error
- dual license -> info
- license override -> warning
- global default license -> info
- global license whitelisting -> info

Signed-off-by: Andre Moreira Magalhaes <andre.magalhaes@collabora.com>