I noticed you started the Elixir SDK for Dagger. Any plan to take it out of experimental stage?
mas03
olivermt
Is this dagger.io ?
I hate what AI has done to the internet.
Opened it to read what I presumed would be a nice pipelines build tool and got five pages of examples to build «agentic software» (open PRs for you based on some LLM crap etc).
We were blocked on a deploy due to gh actions not being able to npm install the other day and it got me motivated to look into more locally reproduceable builds.
Edit: buildkite is what I have had on my TODO-list to look at for the record
1
binarytemple
Yeah, Dagger.io - used it on my last project. It was great.
What I like about it is how it’s pushing secrets management and private project dependencies as first-class citizens, as it’s such a pain to get that stuff working in GitLab, as so many less experienced folk see no issue with a separate local build config and a remote build config full of GitHub/GitLab/CircleCI specific seas of platform-specific YAML.
Another nice thing about Dagger.io is that they make it very easy to debug the build (interactive console) so you don’t need to get into 20-minute “change YAML, trigger build event, view the logs” hell cycles.
The AI/LLM hype at the moment is so jading; lots of it’s garbage, and every company under the sun is trying to convince investors they have their own HAL 9000 system when they’ve just got an even worse interface to their systems than the janky React (insert FANG company the developer wished they were working at when they selected the tech) system that preceded it.
2
D4no0
Like how it is better? Gitlab has nothing special for dealing with that, especially when you have your custom runners, it’s all about that runner machine having the right keys to access that private stuff.
0
wingyplus
It should be within this year.
There is a lot of works to do (documentation, api polish, integration tests, catch up features, etc). But you can start using it and give a feedback to me (and the community). 
1
binarytemple
Dagger.io’s primary win (if you fully commit to it) is having composable code that works for both build and CI environments, offers cacheability, and is easy to debug (locally or even running on CI infrastructure).. While GitHub has supported secrets and SSH mounting for many years—allowing a single Dockerfile to serve both local and cloud needs—GitLab is somewhat lacking in this area.
GitLab doesn’t natively support mounting SSH secrets without manually configuring Docker-in-Docker, which often leads developers to simply copy and paste GitLab configurations rather than getting a Dockerfile working for both desktop and CI use, resulting in configuration divergence. When working with private dependencies, using your desktop Dockerfile to build CI images becomes particularly cumbersome in GitLab.
I’ve worked with the Go bindings rather than the Elixir language binding, as I found the former straightforward to understand and implement. I hope to avoid being drawn into a debate about the comparative merits and challenges of these platforms—GitLab certainly has many commendable features (plantuml support is excellent for example, as is the lack of Microsoft ownership) despite the specific limitations I mentioned.
1
Schultzer
Yeah, I run Act on macos with docker, great for testing Actions before pushing them. Although I’ve been looking into something different like https://tart.run to avoid docker completely.
2
dimitarvp
Schultzer
It’s uses the new virtualization framework that was launched with Apple Silicon. It’s not a replacement for docker, since it only works for Mac, but I like to avoid docker completely and just run as close to what my servers runs.
1
binarytemple
Had a lot of problems with Act, very glitchy and downloaded the world, and not well supported by GitHub, this frustration of trying to get Act to work was actually what set me off in the first place looking for an alternative, and eventually a provider agnostic alternative.
2