shykes

17 ms·

211.
by shykes 4y ago
It's up to you how granular you make your CI configuration. Much of it depends on the context and how your team works. If you've already found yourself integrating a Makefile in a CI job, and figuring out the best mapping of Make
212.
by shykes 4y ago
There's some of that. CUE is incredibly powerful, but it can be polarizing. But the fundamental problem is that developers don't want to learn a new language to write CI/CD pipelines: they want to use the language they alread
213.
by shykes 4y ago
Dagger and IaC tools (AWS CDK, Terraform, Pulumi) are very complementary. Here's a livestream of Nic Jackson (devrel at Terraform) using Dagger and Terraform CDK together to build and deploy an application: https://www.youtu
214.
by shykes 4y ago
Hi everyone, Dagger co-founder here. Happy to answer any questions. We also released an update to the Go SDK a few days ago: https://dagger.io/blog/go-sdk-0.4
215.
by shykes 4y ago
Yes, in the example above, "golang:latest" is the name of a docker image: the equivalent in Dockerfile would be "FROM golang:latest". You can use Dagger to pull any image at all from any registry, including any base linu
216.
Dagger Go SDK 0.4(dagger.io)
2 points by shykes 4y ago|0 comments
217.
by shykes 4y 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.
218.
by shykes 4y 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
219.
Dagger Go SDK: develop CI/CD pipelines as Go, run them in containers(docs.dagger.io)
4 points by shykes 4y ago|0 comments
220.
by shykes 4y 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 diffe
221.
CI pipelines should be code: introducing the Dagger Go SDK(dagger.io)
14 points by shykes 4y ago|8 comments
222.
by shykes 5y ago
Yes, Dagger can be integrated in a devcontainers workflow. How much or how little is done by Dagger is up to you.
223.
by shykes 5y ago
Yes IDE integration are a great idea and we plan on building those too. What IDE would you personally want to integrate, and what actions would you want it to support?
224.
by shykes 5y ago
I agree and I think we will get there. I see CI/CD as one of several “micro-categories” that no longer makes sense standalone, and will gradually merge into a single mega-category. Those include, off the top of my head: continuous inte
225.
by shykes 5y ago
It seems very similar. The main difference (from a cursory look at their docs) is that toast uses YAML as a frontend, and Docker Engine as a backend. Whereas Dagger uses CUE as the frontend, and Buildkit as a backend.
226.
by shykes 5y ago
Good question. Let me provide a more detailed answer in terms of concurrency and parallelism . To paraphrase Rob Pike's excellent explanation: - Concurrency is the breaking down of a program into pieces that can be executed indepe
227.
by shykes 5y ago
We did. Each action can be written in the language of your choice (I personally use bash) then wrapped in a declarative CUE config (typically quite short). Then you compose declaratively in cue. Here is an example of a package to deploy to
228.
by shykes 5y ago
Yes, that’s right. Especially since you’re probably running the same dagger actions all day long in development, upstream from CI.
229.
by shykes 5y ago
It can be a “megastep” in jenkins, but it doesn’t have to. It could be one individual step that happens to run on Dagger. Both work equally well. In the “megastep” approach, it boils down to which tool can provide the most useful informatio
230.
by shykes 5y ago
You can (and people do) run Dagger on top of Tekton, in the same way that you might run a Makefile or shell script on top of Tekton. The benefit is that you are less tied to a particular runtime environment. The same Dagger pipeline can run
231.
by shykes 5y ago
You still need to manage the size of your cache, since in theory it can grow infinitely. But it’s a different problem than managing regular Docker images, because there are no named references to worry about: just blobs that may or may not
232.
by shykes 5y ago
That is a common pattern. Dagger is essentially a more modern iteration on that pattern.
233.
by shykes 5y ago
> When you're threatening people with legal action you need to be clear, and right now the text on that page is not, according to what you're saying here. That's good feedback, thank you. We can try and make it clearer a
234.
by shykes 5y ago
I can't speak to Earthly's choice of license (and am not familiar with BSL). But can confirm that we have no intention of changing licenses, and if we did, it would be for another OSI-approved license. Our monetization model follo
235.
by shykes 5y ago
I stand corrected! Earthly developers if you read this, I'm sorry for misremembering. I would correct my original post if I could.
236.
by shykes 5y ago
I can sympathize, but want to clarify that, although I did found Docker, I left 4 years ago. Dagger is not affiliated with Docker in any way. Also: Dagger can integrate with Podman, Buildah and Cosign :)
237.
by shykes 5y ago
Yes, that's a reasonable approximation.
238.
by shykes 5y ago
Pulumi is great and we think of it as complementary to Dagger: one is focused on managing infrastructure, the other on deploying applications on top of the infrastructure. They are more similar in their choice of language than you might thi
239.
by shykes 5y ago
> > We will not rely on unusual licences to restrict competitors from running Dagger as a service. > Your "Trademark Guidelines" appear to contradict you: They do not. Software licenses and trademark guidelines are two
240.
by shykes 5y ago
> also, is there a gui? Not at the moment, but we plan on offering one (optionally) as a web service.

More ›