CI pipelines should be code: introducing the Dagger Go SDK

by shykes • 4 years ago

14 8 4 years ago

shykes4• 4 years ago

Hi everyone! Dagger co-founder here. This is an exciting new step in Dagger's roadmap. We believe CI/CD pipelines should be developed as code, and run in containers. Realistically this requires maintaining a bunch of SDKs in different languages. Today we are introducing a Go SDK, but expect more SDKs from us soon!

Happy to answer any questions here, on Discord or Github.

Special thanks to the Docker team for continuing to maintain buildkit, which is the underlying tech that makes much of Dagger possible!

codewithcheese• 4 years ago

Hi, last time I checked out dagger, plans were built using CUE, has CUE been dropped? Dont see any mention of CUE anywhere. If so, is there a write up about the change of plan? Thanks

shykes4• 4 years ago

CUE support is not dropped: you can now choose between the Go or CUE SDK, depending on your preference. Both are visible in the docs: https://docs.dagger.io

The underlying Dagger Engine is language-agnostic: all SDKs eventually send requests to the same API, which is what makes this multi-language approach possible.

Docs for Go SDK: https://docs.dagger.io/sdk/go

Docs for CUE SDK: https://docs.dagger.io/sdk/cue

nh23423fefe• 4 years ago

thought this was about dependency injection

melezhik2• 4 years ago

I did not see how one can build against different Linux distors. The code example shows "golang:latest" image only ...

shykes4• 4 years ago

Think of it as Dockerfile but in Go. You can pull any image, or build your own on the fly. Everything you can do in a Dockerfile, you can do in the Dagger Go SDK.

melezhik2• 4 years ago

That is all ok, however Dockerfile means one builds an image for a certain OS/Linux distribution ( base image or FROM directive) , not just a specific Golang version, I did not find how one can do so in the provided examples

CI pipelines should be code: introducing the Dagger Go SDK

Related Stories