The new #earthlyci 0.7 is looking pretty stellar.😎 I been growing to really like using earthly for ci pipeline writing. The local usecases make it such a powerful way to work.

Earthly cleaned a considerable amount of cruft. When when using #nix, the ci was always hackiest part. Now, at least the hacks are digestible. 😁

https://earthly.dev/blog/earthly-v0-7/

Spent last weekend really trying out #earthlyci. 🌎 I can see this being very useful for set up that is already building an OCI image. But it can also useful for cross tooling needs for your ci. Especially if the mess needs to work outside of #nix. 😅

https://earthly.dev/

The more I think of it, the more #daggerio and #earthlyci make more sense for reproducibility of your ci. 🤔

It isn't just enough that you have your code reproducible anymore. You need all your ci to have the same standard.

@andre_601 @osfanbuff63 those are really good points, but also reasons why you may not want to become so tightly dependent to a ci tool. You are stuck in what you can export out.⚰️

Personally, I've gone the route of making my ci as agnostic as possible. That means more work upfront on my end. But the net result is that I'm not tied to a single approach.

There's also tooling precisely for this like #earthlyci and #dagger.
https://fosstodon.org/@thatayush/109672777724150908

CI builds get so utterly complicated. It's why I favor #nix. You get an absolute with all the dependencies, cache, environment, and releases. 😅

Still, options are now alone to do nix on CI. A small list of tools that to help in this world:

- #daggerci code ci
- #earthlyci dsl ci
- #nix dsl for artifacts
- #dhall yaml generation
- #cue yaml generation

@thatayush though going through #earthlyci docs, it seems I could do something like nix build inside it with using nixos image. Though at that stage, I'll have 3 layers of cache. Earthly, podman, and nix itself... 🤣