This message was deleted.
# platform-toolbox
s
This message was deleted.
e
Thanks Maciej, glad you enjoyed it! Yeah part of what BuildKit enables is really complex builds, but that has a side effect of generating lots of information that can be difficult to parse through, very much including digging errors out, so completely agree BuildKit needs improvement there. As of right now, I wouldn't say that CUE specifically has much of an impact; it's sort of like a new "frontend" to BuildKit, but a lot of the output ends up the same. At Dagger specifically we definitely want to improve this situation. One way we're pursuing that is adding support for viewing the output of Dagger builds in a web interface, which gives us much more flexibility in terms of displaying errors clearly. But this will be an ongoing project, lots of room left. Does that answer your question?
m
Unfortunately yes 🙂 Thank you!
Most of the build tools (e.g. Gradle) have built-in reporting. Usually an HTML or something like JUnit XML, which can be displayed in most of the CI/CD web interfaces. I just wanted to show it even (or especially!) when tests are failing.
e
Ah totally! Yeah the ability to seamlessly integrate with existing error reporting tools would be awesome, it's a great idea.
I'm actually going to open an issue about that in our Dagger repo since it's definitely something we should do 🙂
👍 1
Opened an issue here, appreciate the idea! https://github.com/dagger/dagger/issues/2603
m
Thank you! Voted 🙂
Maybe you can link it with the moby/buildkit issue I've mentioned (if it is relevant).