4 ms·

I've been migrating some Workflows to dagger.io. So far it's amazing.

redhale 3y ago
Thanks for sharing, I was unaware of dagger.io! I'm curious now -- are there any other alternatives with similar philosophy/benefits?
- maestrae 3y ago
  There's earthly.dev but like previous commenters, I went with dagger because i prefer its Apache 2.0 license over earthly's BSL.
  - adamgordonbell 3y ago
    Earthly is MPL 2.0 now. I work for earthly and people didn't like BSL so we listened and changed.
    - paradox460 3y ago
      Earthly is legitimately one of the coolest projects I wish I could use. But entrenched velocity in existing systems makes it a difficult pitch
      - adamgordonbell 3y ago
        That's great to here! Sometimes people find just starting with a messy part of the build process, or starting to replace dockerfiles here and there can add value, without having to change the world.
      - marcosnils 3y ago
        Hey, Dagger employee here. This exactly is one of the the main design decisions of Dagger. We're not expecting companies and/or projects to perform a full migration to it, that's why we generally recommend starting by wrapping different parts of your pipeline and move on from there. Unlike other solutions, Dagger allows you to keep using your existing tooling and reuse Dockerfiles (https://docs.dagger.io/quickstart/429462/build-dockerfile/#reuse-existing-dockerfiles https://docs.dagger.io/quickstart/429462/build-dockerfile/#r...) while slowly transition your pipelines to code.
  - redhale 3y ago
    Thanks for sharing, will definitely check this out!
- tao_at_garden 3y ago
  Yes, there's us over at https://garden.io https://garden.io! We're big believers in pipelines that run anywhere. I even made a short little video that should give you the gist. [1] Some of the short-list of differences: we use YAML for our configuration language, Dagger can use full-fat languages to define its pipelines. Our feature scope is broader: you can use us to vend IDP-like stacks to your developers if you're a Platform Team; we make development with remote Kubernetes clusters very easy, including all the remote image builds; and we have a number of integrations so you can bring your IaC tool of choice (Pulumi, Terraform) into your pipeline and set up service -> infra dependencies. [1] https://www.youtube.com/watch?v=JFnan6s2cDg https://www.youtube.com/watch?v=JFnan6s2cDg
  - redhale 3y ago
    Thanks for sharing, will definitely check this out!
andthat 3y ago
Same here, it's so liberating! I'm also using a Magefile to run the pipelines (written in Go) locally.

Thanks for sharing, I was unaware of dagger.io! I'm curious now -- are there any other alternatives with similar philosophy/benefits?

maestrae 3y ago
There's earthly.dev but like previous commenters, I went with dagger because i prefer its Apache 2.0 license over earthly's BSL.
- adamgordonbell 3y ago
  Earthly is MPL 2.0 now. I work for earthly and people didn't like BSL so we listened and changed.
  - paradox460 3y ago
    Earthly is legitimately one of the coolest projects I wish I could use. But entrenched velocity in existing systems makes it a difficult pitch
    - adamgordonbell 3y ago
      That's great to here! Sometimes people find just starting with a messy part of the build process, or starting to replace dockerfiles here and there can add value, without having to change the world.
    - marcosnils 3y ago
      Hey, Dagger employee here. This exactly is one of the the main design decisions of Dagger. We're not expecting companies and/or projects to perform a full migration to it, that's why we generally recommend starting by wrapping different parts of your pipeline and move on from there. Unlike other solutions, Dagger allows you to keep using your existing tooling and reuse Dockerfiles (https://docs.dagger.io/quickstart/429462/build-dockerfile/#reuse-existing-dockerfiles https://docs.dagger.io/quickstart/429462/build-dockerfile/#r...) while slowly transition your pipelines to code.
- redhale 3y ago
  Thanks for sharing, will definitely check this out!
tao_at_garden 3y ago
Yes, there's us over at https://garden.io https://garden.io! We're big believers in pipelines that run anywhere. I even made a short little video that should give you the gist. [1] Some of the short-list of differences: we use YAML for our configuration language, Dagger can use full-fat languages to define its pipelines. Our feature scope is broader: you can use us to vend IDP-like stacks to your developers if you're a Platform Team; we make development with remote Kubernetes clusters very easy, including all the remote image builds; and we have a number of integrations so you can bring your IaC tool of choice (Pulumi, Terraform) into your pipeline and set up service -> infra dependencies. [1] https://www.youtube.com/watch?v=JFnan6s2cDg https://www.youtube.com/watch?v=JFnan6s2cDg
- redhale 3y ago
  Thanks for sharing, will definitely check this out!

andthat 3y ago

Same here, it's so liberating! I'm also using a Magefile to run the pipelines (written in Go) locally.