Hi,
On Fri, 9 Sept 2022 at 15:15, Tomeu Vizoso <tomeu.vizoso@xxxxxxxxxxxxx> wrote:
Also include a configuration file that points to the out-of-tree CI
scripts.
I think this para is outdated given ...
v8:
- Move all files specific to testing the kernel into the kernel tree
(thus I have dropped the r-bs I had collected so far)
- Uprev Gitlab CI infrastructure scripts to the latest from Mesa
But equally - and sorry for not jumping on the IRC (?) discussion as I was in the middle of other stuff when it came up - I'm don't think this is the right plan.
Mesa having all its CI in-tree makes sense, because merges happen rapidly to a single canonical tree. If the scripts need to be changed for whatever reason, we can merge something in under an hour and everyone immediately gets it. DRM is quite different though, given the forest of trees we have and the long merge paths between them. I worry that merging the CI scripts in-tree - especially for our initial attempt at it, when we're likely to need to make quite a lot of changes before it settles down to become a stable system that works for everyone - is shooting ourselves in the foot by limiting our flexibility.
Given that it's currently very dependent on fd.o infrastructure (published ci-templates, the registry, the specific-tag runners for Collabora/CrOS DUTs, etc), there isn't much of a portability gain in bringing the scripts into the tree either. It's a good goal, but not where we are today.
Cheers,
Daniel
