Live data from Hacker News

Dagger Python SDK: Develop Your CI/CD Pipelines as Code

dagger.io

91–92 of 92 posts

Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code

#91
post #73

Earlier quoted context omitted.

Dagger originally started with CUE, and is still powered by it under the hood, which has the constructs you mention, while also being turing incomplete. I don't understand this move to define infra and CI imperatively, and tool vendors moving to support umptine languages for their users... Say what the world should look like, not how to get there?

Thanks for your work on cue (cuetorials)! It's really a blessing for something like CUE to come (I've had some exposure to gcl/bcl and if it wasn't for the internal diffing tool, I would've been lost - https://pure.tue.nl/ws/portalfiles/portal/46927079/638953-1.... ) I've even started prototyping something like bazel/gn but based on cue, but no time to finish it up.

Software is never finished... keep moving it forward when you can!

Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code

#92
post #83

This post is for the python sdk, but the golang SDK is fantastic too. Complete gamechanger to be able to move away from jenkins groovy CPS hell

Could you share some information about how you're doing this? How do you create Jenkins stages, push artifacts, test results, etc.? Cheers

3 days later a response.

We have extensive jenkins pipelines, and the "platform team" supports multiple types of build/release models. Most of the infrastructure is written in TF. * 3 languages * 5 "types" (http/cron/flink/etc)

As such we've got huge groovy libraries that codify the build/release process.

I'm using dagger to re-implement most of these libraries, but in a way that I can test and develop locally without getting into tiny commit/rebuild hell.

Using a language like golang with an engine like buildkit behind it, allows me to more easily test each step of the pipeline, without running the whole thing.

Post reply on HN