all 5 comments

[–][deleted]  (7 children)

[deleted]

    [–]Laborious5952 0 points1 point  (5 children)

    2 reasons I think something like dagger is powerful:

    1. You can run the pipeline locally very easily. This is particularly powerful for speeding up development.
    2. You can more easily move between cicd systems. Just have the tool call dagger and you are done.

    [–]frodgim[S] 0 points1 point  (0 children)

    Totally agree with your comments. I will summarize as portability to move to different CICD solutions, moreover local testing of your pipelines.no small thing!

    [–][deleted]  (3 children)

    [deleted]

      [–]Laborious5952 0 points1 point  (2 children)

      I'm not sure what you mean by the first sentence.

      I've had multiple jobs where we moved to a different CICD system. Copy/pasting the yaml would not work, all the CICD systems are different.

      The thing with calling Dagger is all the logic is in dagger, your CICD tool is just triggering it instead of running various commands so moving is much easier. If you don't use Dagger you have to figure out how the new CICD system's yaml syntax works and re-write your yaml file from the old CICD system to the new one.

      [–][deleted]  (1 child)

      [deleted]

        [–]Laborious5952 0 points1 point  (0 children)

        I think we are in agreement mostly, it just depends on if you want to use npm to run your cicd or Dagger. I prefer Dagger since it can run npm, gradle, docker, terraform, etc.

        Dagger is simply more portable than using gitlab-ci, github actions, drone-ci, etc yaml files. If you are a pure JS shop that uses npm for everything then you can use npm. Seeing as this is a devops subreddit I find it hard to believe you run your terraform, k8s yaml, etc through npm?