February 2025 Summaries

Puzzle, a consulting firm focusing on the automation of IT infrastructure using Kubernetes, was struggling with their CI/CD pipeline due to lack of direct control over the underlying cluster. The team had to rely on the operations team for administrative tasks, adding unnecessary time and overhead to their day-to-day work. To address this issue, they decided to self-manage the Dagger Engine deployment by running it in virtual machines (VMs) on Kubernetes using KubeVirt. This setup allowed them to scale up the number of VMs as needed, upgrade Dagger without requiring admin permissions, and simplify CI configuration for their projects. The new setup has benefited both the CI/CD team and development teams, increasing velocity and simplifying workflow configuration. With this setup, Puzzle is now able to integrate their CI infrastructure into their existing GitOps setup, manage the entire VM themselves, and perform upgrades and testing much faster.

The Dagger Java SDK is a new way for Java developers to leverage Dagger to build and run automation workflows. It brings the flexibility of Dagger's API to Java, enabling users to define and execute workflows in Java without needing to switch languages. The SDK allows developers to manage automation, orchestrate services, and streamline workflows more easily, with features such as caching and portability. It also enables interoperability with other Dagger SDKs, including Go, Python, and TypeScript. The Experimental Dagger Java SDK is currently available for early adopters to test, provide feedback, and help shape its future. With the Java SDK, developers can define fully portable execution workflows that run anywhere, using just a few lines of Java code.

Dagger 0.16 has been released with several features and improvements that simplify workflows, enhance security, and provide a smoother overall experience for users. The update includes secure secrets management with integrations to HashiCorp Vault and 1Password, allowing teams to securely retrieve credentials at any stage of execution without preloading them into their environment. Additionally, performance improvements have been made, including faster module loading times, reduced extraneous files loaded from the source repository, and improved cache utilization. The update also introduces a new engine configuration file, `engine.json`, which simplifies the format and adds Dagger-specific fields. Furthermore, Dagger now supports floating-point numbers inside the engine, enabling more precise calculations in pipelines that require numeric operations. Overall, the release reflects feedback from the community and prioritizes features and fixes for future improvements.

The Dagger PHP Community SDK is a new tool that allows developers to automate their workflows using PHP. It brings the flexibility of Dagger's API to PHP, enabling users to define automation workflows in PHP without having to switch languages just to script tasks. The SDK provides features such as caching and portability, allowing users to run their workflows locally or remotely with full reproducibility. It also enables users to easily compose and reuse logic across projects, making it easier to maintain automation modular and keep it up-to-date. The PHP SDK is a community-driven project maintained by passionate Dagger users, including Paul Dragoonis, John Charman, and Chris Riley. To get started with the SDK, developers can check out the PHP SDK on GitHub, follow the Dagger Quickstart, and join the Dagger Community on Discord. The PHP SDK is just the beginning, and it will continue to evolve with the help of contributors like users.

The author of this blog post replaced their React frontend with a WebAssembly (WASM) based interface built in Go, a programming language they are familiar with. The goal was to unify the codebases for both Dagger Cloud and the terminal UI, eliminate duplication, and deliver a crisp and snappy Web UI while maintaining performance and consistency across all interfaces. Despite some initial challenges, such as the memory usage limit of WASM applications, the team overcame these obstacles through careful design and optimization. The new interface has resulted in improved performance, lower memory usage, and a more consistent user experience. However, the author notes that this approach may not be suitable for everyone and cautions against making front-ends in Go unless you have a strong reason to do so.