Gitlab CI Dashboards and retirement of build.kde.org

[Ben Cooksley]

On Sat, Sep 3, 2022 at 10:12 PM Johannes Zarl-Zierl <johannes at zarl-zierl.at>
wrote:

> Hi Ben,
>

Hey Johannes,


>
> Thanks for the reminder!
>
> On a related note: would it be possible to add badges for CI/CD status to
> repositories?
>
> Quite a few projects (used to) have this in their README.md, but if I
> unterstand the situation correctly, Gitlab CI doesn't produce a
> build-status badge that one can link to.
>
> Examples:
>
> https://invent.kde.org/multimedia/kdenlive/-/blob/master/README.md
>
> https://invent.kde.org/graphics/kphotoalbum/-/blob/master/README.md
>
> https://invent.kde.org/graphics/digikam/-/blob/master/README.md
>

Gitlab provides a limited selection of badges - which can be found at:
- https://invent.kde.org/multimedia/kdenlive/badges/master/pipeline.svg
- https://invent.kde.org/multimedia/kdenlive/badges/master/coverage.svg
- https://invent.kde.org/multimedia/kdenlive/-/badges/release.svg

(replace project path and "master" as appropriate)

Note that the Release badge relies on the Gitlab Releases feature being
utilised, so that will likely not be usable for any of our projects.
Likewise, our Cobertura coverage job currently doesn't have the necessary
regular expression configured so that one also won't work - however the
general "Pipeline" one should work fine.

Unfortunately Gitlab does not support generating per job badges based on
job names.


>
>
> Cheers,
>
>   Johannes
>

Regards,
Ben


>
> Am Samstag, 3. September 2022, 06:45:31 CEST schrieb Ben Cooksley:
>
> > On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley <bcooksley at kde.org> wrote:
>
> > > Hi all,
>
> > >
>
> > > This evening I completed the necessary setup required to complete our
>
> > > Gitlab CI dashboards, which can now be found at
>
> > > https://metrics.kde.org/dashboards/f/aNxvXJW4k/gitlab-ci (KDE
> Developer
>
> > > account login required)
>
> > >
>
> > > These allow any developer to get a view on the current CI status of
>
> > > projects and groups of projects on a branch and platform basis - and
>
> > > should
>
> > > hopefully provide useful insight into the overall status that can
>
> > > currently
>
> > > be obtained from Jenkins.
>
> > >
>
> > > As this was the last thing holding us back from shutting down
>
> > > build.kde.org, i'd like to proceed with retiring and shutting down
>
> > > build.kde.org as soon as possible so the capacity it occupies can be
>
> > > released and reallocated to Gitlab.
>
> >
>
> > As previously indicated, I have now shutdown build.kde.org along with
> the
>
> > domain that supported it's version of the CI tooling.
>
> > The repository containing that tooling has now also been archived, and
> the
>
> > former build.kde.org domain has been redirected to metrics.kde.org.
>
> >
>
> > The server which was acting as a builder for build.kde.org will be
> rebuilt
>
> > in the coming days and reallocated to support Gitlab CI workloads.
>
> >
>
> > > If anyone would like to experiment with customised views for their own
>
> > > purposes (where the above provided ones are insufficient) please file a
>
> > > Sysadmin ticket.
>
> > >
>
> > > Please let me know if there are any questions on the above.
>
> > >
>
> > > Thanks,
>
> > > Ben
>
> >
>
> > Thanks,
>
> > Ben
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20220904/7e5479d1/attachment.htm>