3 ms·
Author is now trying Bazel I'm going the Dagger path This CNCF talk covers both: https://www.youtube.com/watch?v=nZLz0o4duRs https://www.youtube.com/watch?v=n
by verdverm 3y ago
Author is now trying Bazel
I'm going the Dagger path
This CNCF talk covers both: https://www.youtube.com/watch?v=nZLz0o4duRs https://www.youtube.com/watch?v=nZLz0o4duRs
- hoherd 3y agoAuthor tried bazel 8 years ago, which is when the article was written. Judging by his GH repos, he's still using Makefiles. https://github.com/dimonomid/bulgaria-freelance-taxes/blame/master/Makefile https://github.com/dimonomid/bulgaria-freelance-taxes/blame/...
- amtamt 3y agoAnyone not working alone, not working on his own projects only, will end up having to use tools created ages ago, but refined gradually, how ever clunky the usage feels along the usage journey.
- mediumsmart 3y agoI was going to comment that I am tired of undated articles. Where did you see when it was written?
- verdverm 3y agoIt's in the URL, I too missed it until pointed out
- esafak 3y agoDo you call bazel from dagger or what? You still need a build runner, no?
- verdverm 3y agoNope, just write code instead of Bazel or Make Everything runs in a container You can of course run whatever tool you want inside containerize workflows with Dagger, which can be much more than a build tool
- esafak 3y agoAre you using a compiled language? IF so, what are you building with? That is the part that bazel optimizes. Once the build artifact is created, you can containerize it with dagger, of course.
- verdverm 3y agoIs the Bazel version consistent across all local dev & build ci? How do tool updates & versions work as developers switch between branches and repos? Run Bazel in Dagger for consistency, or more generally build your binary in a container with Dagger using whatever tools you like. One main point of Dagger is the consistency between local & cloud for the build scripts, whereas containers have always been thought of as for consistency when running locally and cloud