At some point we may rename the main branch, so prepare for that.

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

Emanuele Aina authored 5 years ago and Sjoerd Simons committed 5 years ago

To quickly check the overall status without scrolling the whole list,
add a section before the report table with data like this:

    packages: 3076, failed: 310, no pipeline: 1

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

For review it's quite useful to have a testbuild with all the artifacts;
but that shouldn't be published to gitlab pages (which overwrites the
"official dashboard"). Just published as artifacts

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

With newer gitlab (as now deployed for Apertis) we can take advantage of
environment variables to determine the gitlab host location rather then
hardcoding it.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Fix after pipelines got moved to buster-gilab-update-job branch

See merge request sjoerd/gitlab-dashboards!1

The script was still relying on pipelines being executed on the release
branch such as `apertis/v2019`, but they got moved to a separate branch
tracking the source distribution, such as `apertis/buster-gilab-update-job`
for Debian Buster.

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