Sorry, it looks like the machine we were using to provide the 'Public' worker on invent.kde.org has fallen over.
Unfortunately we don't have a contact for the hoster of that machine so we may be a while without this service - Gitlab CI was for demo/testing/evaluation purposes only so this shouldn't have any production impacts for people.

I disagree, this is crucial to Okular development, getting a pre-commit CI for Merge Requests has helped us catch already quite some failure to build with old Qt, breaks of unittests, etc.

I would really appreciate having CI back.

We're rich now and we can't spend money on sprints/Akademy because the world is ending so maybe we cna spend some in a proper builder for gitlab given it's supposed to be the future?

The problem is we're halfway between the old world and the new world. The builder that was connected to Gitlab was for demonstration and testing purposes only to see how it would work.

You've gone ahead and used a demo service for production purposes which is unfortunate.
The proper implementation is still on it's way.

Money isn't the issue here - it's a case of system maintainability as we're looking after quite a bit more infrastructurally on a temporary basis as we cross the gap from Gitolite/Phabricator/Jenkins to Gitlab.

Mirroring on gitlab might be a good short term work around for those who need to run custom images. KDiff3 has done this for some time. There will be commit shortly to switch back while the outage is going on. For my use case its largely a cannery to tell me when a build fails after a commit is done. The image I use has a somewhat older kf5 framework on it and recently paid off when someone updated the documentation format unintentionally assuming a very recent kf5 version was in use.