Historically kernel development had very little of this kind of systematic, automated testing; it relied on careful review of pull requests followed by the core developers running regularly-updated builds on their own machines.
I thought it was in the spirit of devops, speeding up development/testing by closing the feedback loop. Also, reducing operational and infrastructure burden or friction.
The idea is good, but the name is wrong. It's like if I made a script that automated using Nodejs & Sonarqube and called it Kagile. There's more to Agile than just using a couple tools; same with DevOps.