hello what is the typical workflow when | Dagger | Page 1

pallid pendant Jul 24, 2023, 3:59 PM

#

Hi @glad yacht 👋 ! Welcome 🙂

The idea is that if you've implemented pipelines with Dagger then folks can run that same Dagger pipeline code (written in your SDK of choice: Python, Node.js, Go, etc) both locally AND in your CI.

This is nice because it helps with the "it works on my laptop! (but not in CI)" or vice versa problems. It also allows folks to have a fast local loop (because of automatic caching) to get everything working and then you can push to CI with a lot more confidence instead of the old model of "push code and go get a cup of coffee, it's going to be 5-20 minutes before CI finds that linter issue or typo".

Another benefit is that you can also iterate quickly while building/modifying the pipeline itself, and app devs and platform folks can collaborate on growing/fixing the pipeline since it's all code that the whole team understands instead of a bespoke YAML or DSL.

glad yacht Jul 25, 2023, 10:17 AM

#

Hi, thank you for taking time answering.

It's perfectly clear. Also one other question :

Golang seems to be most promoted language to use Dagger with, is there a particular reason ? Thanks 😉

pallid pendant Jul 25, 2023, 2:39 PM

#

A lot of the code to implement Dagger is in Golang and our own CI is currently written with the Dagger Go SDK, but we also have team members who are more comfortable in Python or Javascript/Typescript and we have users in production with all three.

We try to give examples of all three in places like
https://docs.dagger.io/7442989/cookbook
https://github.com/dagger/examples

The nice thing is that all of the Dagger SDKs (including the experimental ones in development like Rust, Elixir, C#/dotnet, Java, etc) all use the same core Dagger GraphQL API in the backend, so have the same capabilities.

Which SDK would you prefer to use? 🙂

glad yacht Jul 28, 2023, 4:16 PM

#

Golang so far is great

#hello what is the typical workflow when