• @worldofgeese
    link
    7
    edit-2
    1 year ago

    My employer, garden.io, offers pipelines you can run anywhere: in GitHub Actions, GitLab CI, locally, wherever! We capture all your dependencies in a dependency graph, then cache all your inputs: builds, tests, run scripts. We’re open source at https://github.com/garden-io/garden

  • @[email protected]
    link
    fedilink
    71 year ago

    I always try to put as little logic into CI-Runner-specific tooling as possible and rather have everything automated via the usual programming language build tooling, which you can run locally.

    • snoweM
      link
      fedilink
      61 year ago

      act is so hard to use and the docs are terrible. Every time I go to use it I give up a few hours later having gotten nowhere. Incredibly frustrating experience.

    • @[email protected]
      link
      fedilink
      11 year ago

      One of the frustrating things with Dagger is that you still have to set up your pipeline tool. Sure, you’re theoretically running the same thing local and remote, but it doesn’t remove much in the way of CI work. Azure stuff is (was?) less supported. And while the move away from CUE was the right one, there’s still a lot of CUE around.