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.
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.
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.
This guy basically duct-taped together ansible, vagrant and terraform scripts to automate provisioning a virtual machine and does some filesystem tests... of an already tested and distributed kernel. And by "any project" I guess the author means any project that doesn't require real hardware or run on non-x86/AMD64 hardware.
This isn't the first time I seen a devops guy duct-tape together the newest fads and then strut like a peacock.
12 comments
[ 2.1 ms ] story [ 41.8 ms ] threadIt literally doesn't. Go out and enjoy your weekend, Sir.
This isn't the first time I seen a devops guy duct-tape together the newest fads and then strut like a peacock.