Today we’re introducing Dagger 0.15, with many usability and performance improvements. We’ve highlighted a few key features below, but there is a

Dagger 0.15: Better errors, Faster filesync, Metrics and much much more…

submited by
Style Pass
2024-12-13 01:30:03

Today we’re introducing Dagger 0.15, with many usability and performance improvements. We’ve highlighted a few key features below, but there is a very long tail of smaller features and bugfixes that add up to a smoother overall experience. Let’s dive in!

Dagger’s job is to help you ship faster. There are several ways we can do that. First, by making your pipelines faster to develop. Second, by making them faster to run. And third, by making their output more readable, so you can act on it.

In this release we are focusing on improving the most important output of your Dagger pipelines: errors. There is a direct correlation between the quality of the errors presented to you, and how fast you can develop.

When the error is produced by a containerized tool, we show the error that matters (“compilation failed at line X”), and skip the parts that don’t (“your tool failed to execute, exit code 2”)

Dagger now transfers files much more efficiently between the host system and the engine container, by caching them more efficiently and avoiding redundant data transfers.

Leave a Comment