Re:Dagger: a new way to build CI/CD pipelines
by dijksterhuis on Wednesday March 30, 2022 @01:03PM
(#30857903)
> 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...?
Re:Dagger: a new way to build CI/CD pipelines
by xrd on Wednesday March 30, 2022 @01:32PM
(#30858272)
Thank you.
It isn't hard to find, but my point was that if you say "using an intuitive declarative language" then a developer will get excited by a code snippet that shows that intuitive developer language. It wasn't there, and I think their post could be improved by having less fluffy language and more code, if they are targeting me, that is.
This link does show the code, but it took a few clicks to get there from your links:
https://docs.dagger.io/1202/plan
At first glance I'm not in love with the language. When I look at the first example, there is a lot I have questions about.
Re:Dagger: a new way to build CI/CD pipelines
by verdverm on Wednesday March 30, 2022 @02:29PM
(#30858973)
The language is CUE, which I think will see mass adoption in config / DevOps in the coming years. So regardless what you think of the language today, it is likely to become important and part of your like in the not too distant future.
https://cuelang.org | https://cuetorials.com
Dagger builds on top of CUE and the (DAG) flow engine therein
Re:Dagger: a new way to build CI/CD pipelines
by dijksterhuis on Wednesday March 30, 2022 @04:04PM
(#30860131)
Oh wow, the validating yaml example on the front page looks super useful. Might try and play with this over the next few weeks!
Re:Dagger: a new way to build CI/CD pipelines
by verdverm on Wednesday March 30, 2022 @05:46PM
(#30861215)
Once CUE clicked for me, there was no going back
Re:Dagger: a new way to build CI/CD pipelines
by xrd on Wednesday March 30, 2022 @02:44PM
(#30859201)
That's great context. That should be added to that doc link right at the top, it would have me feel much more safe about investing the time to learn it!
Re:Dagger: a new way to build CI/CD pipelines
by verdverm on Wednesday March 30, 2022 @05:45PM
(#30861203)
CUE has good pedigree, the creator Marcel wrote the prototype for Borg (k8s), worked on both Google config languages, and worked on the Go team. CUE is how he thinks those Google config languages should have been designed.
Re:Dagger: a new way to build CI/CD pipelines
by KingEllis on Wednesday March 30, 2022 @01:23PM
(#30858160)
Another starting point: https://github.com/dagger/dagger/tree/main/ci
Re:Dagger: a new way to build CI/CD pipelines
by topher200 on Wednesday March 30, 2022 @01:04PM
(#30857907)
There's some code examples in their docs: https://docs.dagger.io/1202/plan
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.