vladaionescu
Joined 14 years ago
Karma
584
Submissions
77
Member since
Sep 9
Recent submissions
Comment · 2 years ago
I would add that 1. Earthly is meant for full CI/CD use-cases, not just for image building. We've forked buildkit to make that possible. And 2. remote caching is pretty slow overall because of the limited amount of data you can push/pull before it becomes performance-prohibitive. We have a comparison in our docs between remote runner (e.g. Earthly Satellites) vs remote cache [1].
Comment · 3 years ago
Nope. Only Earthly CI is.
Comment · 3 years ago
Founder of Earthly here - besides the build debugging difficulty, I would add that modern CI/CD repeats a lot of steps: downloading, installing and configuring dependencies, making things much slower than they should be.
We built Earthly [1] to tackle these two problems specifically. We're open-source (10k stars).
[1]: https://earthly.dev
Comment · 3 years ago
This is the main reason we built Earthly: run your builds locally, and get consistency with the CI.
Comment · 3 years ago
Hello HN,
Vlad, creator of Earthly here! Earthly is an open-source build automation tool. We use containers to make builds consistent across any environment, thus eliminating difficult to reproduce CI failures, because you can run your CI build on your laptop every time.
Second, isolation means that dependencies between steps need to be explicitly declared, and with this knowledge, earthly can infer parallelism.
Third, containerization gives caching abilities. We can tell if nothing’s changed since a previous run, and earthly can cache steps across build runs or even across machines. This results in massive speed gains. 2-20X, depending on the setup.
We trended with Earthly on HN a few times before, but we made significant progress since we last had a Show HN entry, 2 years ago [1]. The biggest part is that we recently launched Earthly Cloud, which includes Earthly Satellites, super fast remote runners that work with any CI. Earthly Cloud includes a generous free tier if you'd like to give it a try.
Comment · 3 years ago
This article is slightly click-baity. The payments are delayed in some cases, not held out altogether. From what I'm hearing so far, Rippling has changed banks over night and has instructed all clients to update the ACH filters accordingly. Only payroll cycles caught in-between will be affected, but even then they are delayed, but not held.
Comment · 4 years ago
Hey HN, author here. We made the switch to open-source to better align our incentives with the community. It was a tough decision in the face of tech-giant monopoly bullying, but I think the pros outweigh the cons in this case. Looking for any kind of community feedback on this. Many thanks!
Comment · 4 years ago
Public / Private is interesting.
Private would not be callable from command line and not be listed in `earthly ls`?
Comment · 4 years ago
The `earthly ls` idea is great. We do have shell autocompletions but that is not quite the same thing. I will add a ticket for that.
Cache misses can be a bit inscrutable. It could be the buildkit GC is running, because disk space is getting scarce, or that some arg or file change caused the cache to be considered invalid.
Caching is an area we will continue to improve. We have a proposal for extended cache mounts here[1].
Thanks for using earthly!
Comment · 4 years ago
Hello HN.
Earthly is a tool for build automation and we just had our biggest release yet.
Earthly is a modern build solution that is similar to a sandboxed makefile. It works with your existing CI and the #1 reason people use it today is to able to reproduce a CI build locally.
Today we promoted a number of important features to GA status in our 0.6 release including:
- WITH DOCKER : Earthly can execute any number of containers in parallel, via an isolated Docker daemon that it starts up within.
- User-Defined Commands: Extract common repetitive build steps into a command you can use across your projects.
- Shared Cache: Earthly v0.6 now provides shared caching. This extends our existing build caching to work in ephemeral CI runners by storing the cache in regular container registries.
Let me know what you think! Feature requests always welcome :)
@VladAIonescu on Twitter. vladaionescu on GitHub.