GitLab

Rollback the GIT_STRATEGY option as Gitlab CI still passes the --depth option to Git with the clone strategy.
To workaround the issues with the newer Git on Android Qt 6.2, for now tell it to ignore the issue.

This will eventually need to be addressed in a more proper manner when we start to head in the direction of running CI as something other than root (which Android Qt 6.2 is coincidentally testing...)
The likely fix will be to use GIT_STRATEGY=none and clone the repository ourselves which is not ideal...

This is achieved by asking Gitlab to fully clone the repository (per https://docs.gitlab.com/ee/ci/runners/configure_runners.html#git-strategy)

In 39c1a135 I removed "stage: test" from the reuse job, but that's actually the
default stage, so my change didn't do anything. Set it to the build stage
explicitly instead.

This will let it run in parallel to actual build jobs instead of waiting for
the build jobs to finish.

This should ensure that hung processes that consume an entire CPU core are not left behind - and reduce the overall performance of that CI worker server until it is cleaned up.

CCMAIL: plasma-devel@kde.org
CCMAIL: kwin@kde.org

add possibility to specify that the pipeline should fail for every platform if the tests fail. So not every new platform must be specified

This is causing annoyingly low CPU utilization sometimes. We can bring it
back and discuss it later but with the current state of the CI queue I want
to disable it asap...

Handle it in Python directly...

Having the reuse job in the test stage means it only runs once the build
jobs pass. This is unnecessarily reducing parallelism. Keeping it in the
build stage will let it run in parallel to actual build jobs.

Using different stages is mainly useful when you need previous stages to
finish successfully (for example if we had separate unit test jobs, the
build needs to succeed first).

Ref !15

This can be configured in .kde-ci.yml per platform, which allows us to
phase this in gradually where possible.

If we delete the entire source directory, we can't upload artifacts such as the junit test report.

CCMAIL: tcberner@FreeBSD.org
CCMAIL: groot@kde.org

If we are running on a work branch where the whole history of another repository is being merged in then the commit we've chosen will have a parent of 0x40 which is invalid

Without the ":latest" the CI rejects this for not being in the list of
allowed images.

As the toolchain arguments differ with Qt5, those are moved to the
corresponding templates. We'll therefore need a matching change to
the seed jobs.