GitLab

Assign them separately to workaround this.

This reverts commit 466681ea.

At the moment it's installing to literaly "$HOME", which then it's never
found by the applications.

Lets see how this goes.

CCMAIL: faure@kde.org

Ref T10423

Fixes T10397

it is pretty safe to kill docker container

Ref T10397

Ref T10397

Adding Quazip as now required by Krita.

Ref T10400

they are running infinitely which hits the timeout of the
runner/executor, on static nodes (windows, freebsd) this results in
lingering process

Currently only master branch gets the builds because extragear projects
are special and doesn't have specific naming pattern for the stable
branch. Or even specific policy, there are projects with

- numbers 1.1
- project name and version (Krita/1.x)
- master branch itself behaving as stable
- no stable branch, just tags

And this is so confusing for templatifying the Gitlab CI jobs, It seems
to me that project might have to define stable jobs themself in their
yml file. It is best way to deal with problem

This is necessary to ensure CI nodes do not become blocked due to hanging tests withing plasma-integration.

Currently, plasma-integration has several tests that make use of KIO slaves directly (skipping KLauncher).
Unfortunately, they do not terminate the slaves prior to the conclusion of the test, resulting in the kioslave processes being left around afterwards.
This is a condition that CTest will not tolerate, leading to it waiting indefinitely for these processes to exit - and in turn blocking all other builds on the CI node in question.
While this is not a major issue in the case of Linux builds, it can quickly become a severe condition in the case of FreeBSD and Windows builds due to those builders being fixed rather than dynamically allocated.

This class of issue (CTest waiting due to resident processes being left behind) has been a major issue as of late and is quickly leading to the CI system becoming unmaintainable due to the level of breakage.
Should it be necessary to ensure the maintainability of the system, withdrawal of execution of tests for all projects is an option currently under consideration.

CCMAIL: plasma-devel@kde.org
CCMAIL: kde-frameworks-devel@kde.org
CCMAIL: release-team@kde.org
CCMAIL: kdevelop-devel@kde.org
CCMAIL: sysadmin@kde.org

This is used to build the snap package.

https://build.kde.org/job/Frameworks/view/Everything%20-%20kf5-qt5/job/prison/job/kf5-qt5%20AndroidQt5.11/1/console

This is the package it is actually after

Fontconfig should give a better warning notice about this...

don't run this on merge requests or forks

also make docker build manual action

- instead of removing the image we just created remove dangling images