A friendly reminder to myself that this needs to be done.
Description
The wiki makes sense I think. I'll add a pile of documentation covering the process of how it works, what causes jobs to be created (DSL + gather-jobs), what controls the steps that are executed (Pipeline templates), and what each step does (the Python helpers) including dependency resolution, the Product concept, etc.
Does it make sense to use the Phabricator wiki rather than Techbase? Kind of curious about the policy of one versus the other. I ended up glancing at https://phabricator.kde.org/w/build-kde-org/configuration/git/ and tried to pull down git://anongit.kde.org/sysadmin/ci-master-config but it didn't work
Oh dear, that part of the documentation is indeed quite out of date.
In regards to the current set of tooling, it all now lives in sysadmin/ci-tooling on our Git infrastructure.