Hello,
On Tue, 7 Apr 2020 15:31:36 +0000 Tim Jaacks tim.jaacks@garz-fricke.com wrote:
[]
My take on this is LAVA is _not_ 'jenkins for testing'. It's simply test executor and you need to postprocess your results yourself.
As far as I understood, SQUAD is a project which brings build results and test results together. Not sure if it supports Jenkins, though:
Thanks, I'm definitely aware of SQUAD. And it's a nice, cheerful explanation of it as "a project which brings build results and test results together". Less cheerful (conspiracy-theoretic? ;-) ) might be: "Some stakeholders might have found LAVA own reporting, etc. capabilities to be lacking. As LAVA is a big and inert project, they decided to prototype a new solution outside of it. Fast forward, and they even advertise writing a standalone frontend using LAVA API as the best solution for everyone's needs, forgetting to mention that it took some 4 years, 3 dedicated developers, and a dozen contributors to get there."
And with all that, there's absolutely no guarantee that what worked for some stakeholders would work for you. Actually, someone who was burned by LAVA 'missing and "not needed"' features, would be cautious to not get into catch-22 by adopting another frontend, find features missing, proposing their addition and getting replies like "Well, it was never intended to be like that".
Identifying the minimal changes required for LAVA itself, and arguing for those changes, seems like a better strategy. Maybe I'm wrong.
[]