[rgilton]

Yep, after spending a few years with gitlab pipelines, my company started migrating over to dagger roughly mid-2024.

We moved to dagger to get replicable local pipeline runs, escape the gitlab DSL, and get the enormous benefits of caching.

We have explicitly chosen to avoid using the "daggerverse", and with that the cross-language stuff. Reason being that it makes modifying our pipeline slower and harder -- the opposite of the reason we moved to dagger.

So we use the Dagger python API to define and run our CI builds. It's great!

Like the other comments on this page about dagger, the move to "integrate AI" is highly concerning. I am hopeful that they won't continue down this path, but clearly the AI hype bubble is strong and at least some of the dagger team are inside it.

I'm speculating that if the dagger team doesn't drop the AI stuff, then the dagger project will end. A fork will pop-up and we'll move to using that. Not an expert (yet!) in the buildkit API, but it seems like the stuff we're benefiting from with dagger is really just a thin wrapper around buildkit. So potentially not too challenging to create a drop-in replacement if necessary later.