Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dagger: a new way to build CI/CD pipelines

dagger.io

Post reply on HN
Print view View original

1–10 of 267 posts

Re: Dagger: a new way to build CI/CD pipelines

#3

Post by xrd »

This seems interesting.

But, I wish there was some code to show me what makes it so radically different. It seems like this is targeting developers (or is it devops team?) and I'm excited about the new language here, but I don't see any examples of code. Code engages both my head and heart.

I am reusing a lot of code in my CI jobs. I have an upload script that I reuse. I have a DEB package script that I reuse across many projects. So, that assertion rings false to me, and seems to indicate there is an unhealthy wall between devops and the developers that prevents shared code. Maybe I misunderstand.

The thing that always bites me is that I have trouble debugging a job that depends on the artifacts from a prior job. My e2e job is flakey, and I'm loathe to fix it, because I have to re-run the entire pipeline, test -> build -> installer, etc to get the final artifact used in the e2e job. I've not figured out a way with "gitlab-runner exec" to run a job later in the pipeline and somehow pass in my own artifacts locally. This would be something (albeit very specific to gitlab) that would make me very excited.

Re: Dagger: a new way to build CI/CD pipelines

#4

Post by shykes »

Hi everyone, I'm one of the co-founders of Dagger (and before that founder of Docker). This is a big day for us, it's our first time sharing something new since, you know... Docker.

If you have any questions, I'll be happy to answer them here!

Re: Dagger: a new way to build CI/CD pipelines

#5

Post by dijksterhuis »

xrd wrote: post #3

This seems interesting. But, I wish there was some code to show me what makes it so radically different. It seems like this is targeting developers (or is it devops team?) and I'm excited about the new language here, but I don't see any examples of code. Code engages both my head and heart. I am reusing a lot of code in my CI jobs. I have an upload script that I reuse. I have a DEB package script that I reuse across…

> But, I wish there was some code to show me what makes it so radically different.

Sorry to be that guy but maybe try the docs page...?

https://docs.dagger.io/

https://docs.dagger.io/1205/container-images

Re: Dagger: a new way to build CI/CD pipelines

#6

Post by topher200 »

xrd wrote: post #3

This seems interesting. But, I wish there was some code to show me what makes it so radically different. It seems like this is targeting developers (or is it devops team?) and I'm excited about the new language here, but I don't see any examples of code. Code engages both my head and heart. I am reusing a lot of code in my CI jobs. I have an upload script that I reuse. I have a DEB package script that I reuse across…

There's some code examples in their docs: https://docs.dagger.io/1202/plan

Re: Dagger: a new way to build CI/CD pipelines

#8

Post by bovermyer »

shykes wrote: post #4

Hi everyone, I'm one of the co-founders of Dagger (and before that founder of Docker). This is a big day for us, it's our first time sharing something new since, you know... Docker. If you have any questions, I'll be happy to answer them here!

So basically, if I want to not write Jenkinsfiles but still use my company's existing Jenkins installation, I can use Dagger?

Re: Dagger: a new way to build CI/CD pipelines

#9

Post by topher200 »

shykes wrote: post #4

Hi everyone, I'm one of the co-founders of Dagger (and before that founder of Docker). This is a big day for us, it's our first time sharing something new since, you know... Docker. If you have any questions, I'll be happy to answer them here!

Congrats on launching!

How mature is this? We have a 20 person team and we're prototyping different pipelines for our next CI/CD pipeline (currently Heroku). Is this ready for production workloads?

Post reply on HN