Cache control for modules | Dagger Blog

Dagger, a tool for executing continuous integration (CI) pipelines, has introduced caching for module functions in its version 0.19.4, enhancing the efficiency of pipeline execution by skipping already completed tasks. Previously, only system functions were cached, but now module functions, which serve as orchestration components, are cached by default, reducing overhead in large pipelines. A new cache control API allows developers to specify which functions have side effects, ensuring that functions like deploy() are executed when necessary, despite caching. This system supports different caching modes, such as default, time-to-live (TTL), session, and never, to accommodate various use cases. Existing projects maintain the old behavior with a backward compatibility feature, while new projects benefit from default caching. Developers can learn more from the function caching documentation or participate in the Dagger community through GitHub and Discord for further engagement and support.