Dagger's role in CI | Dagger | Page 1

quartz bramble Apr 6, 2022, 6:25 AM

#

Probably doesn't make a lot of sense to do that. Dagger isn't useful as a CI orchestration tool the way that Azure Pipelines (or Github Actions or Gitlab Devops or Jenkins or Concourse or CircleCI or etc etc) is.

Dagger is more like a superpowered Makefile. You can bundle all the meat and potatoes of your build test deploy cycle in Dagger, then have your CI pipelines run dagger do build test deploy

real chasm Apr 6, 2022, 6:33 AM

#

Oh, I see, so the Azure pipelines would actually drive Dagger?

quartz bramble Apr 6, 2022, 6:33 AM

#

Correct

#

The advantage is that if your org ends up moving away from Azure and you have to support the same application but no longer have ADO to do it with, you can quickly hack up a Jenkinsfile or a .gitlab-ci or a whatever that does the same thing because all the logic is in this platform-agnostic Dagger plan

#

There's also a subjective argument to be made that Dagger plans are easier to read and reason about than typical imperative pipelines so you're less likely to make mistakes during development. Being able to run your Dagger plan locally helps with that, too.

real chasm Apr 6, 2022, 6:45 AM

#

Yes, absolutely. Also, some of our Azure pipelines need to be recreated anyway, so I'm planning on just doing them in dagger.

#

I'm going to start off with my pet project, which is just a go app and a Maria dB.

fossil meadow Apr 6, 2022, 6:46 AM

#

Great explanation @quartz bramble 🙂

#Dagger's role in CI