3 ms·

This is a misleading title. Being yet another CI tool is not the same thing as being a cross platform version of Github Actions and Gitlab CI. A cross platfor

This is a misleading title. Being yet another CI tool is not the same thing as being a cross platform version of Github Actions and Gitlab CI. A cross platform version of Github Actions would allow you to run your actions using your own tooling.

dboreham 3y ago
Also this exists: https://github.com/nektos/act https://github.com/nektos/act which is conveniently packaged in a GH-a-like system by: https://gitea.com/gitea/act_runner https://gitea.com/gitea/act_runner in https://github.com/go-gitea https://github.com/go-gitea
- tao_at_garden 3y ago
  And there's us, https://garden.io https://garden.io, that does totally portable CI pipelines with caching from builds to tests: https://github.com/garden-io/garden https://github.com/garden-io/garden I made an irreverent short on why your CI pipelines ought to be portable and runnable locally. Number one reason? Give your developers their time (and sanity) back. Pushing to Git in the inner loop disrupts flow and shatters attention. https://www.youtube.com/watch?v=JFnan6s2cDg https://www.youtube.com/watch?v=JFnan6s2cDg
  - dosisod 3y ago
    Nice product! I haven't heard of Garden until now. Adding a CLI for Cicada has been on my todo list for a while, and is long overdue! This should be easy enough to do.
  - eysi 3y ago
    Another Gardener here :) Just to add to what Tao was saying, our pipelines are not only portable but also "smart". Instead of having to specify every step of a job—either in code or config—you instead tell Garden that it's e.g. a build of type container, or a deploy of type Helm, and our plugin system figures out the rest (of course with escape hatches when needed). We also track the files that go "into" each job and cache the results, so the same job never has to run twice if the code doesn't change. So if you have a large distributed system and a change only affects a small part of it, you don't need to re-run everything. It can save _a lot_ of time. Unrelated, but love that the Cicada team created a Treesitter grammar for Neovim!
deleted 3y ago
[deleted]

dboreham 3y ago

Also this exists: https://github.com/nektos/act https://github.com/nektos/act which is conveniently packaged in a GH-a-like system by: https://gitea.com/gitea/act_runner https://gitea.com/gitea/act_runner in https://github.com/go-gitea https://github.com/go-gitea

tao_at_garden 3y ago
And there's us, https://garden.io https://garden.io, that does totally portable CI pipelines with caching from builds to tests: https://github.com/garden-io/garden https://github.com/garden-io/garden I made an irreverent short on why your CI pipelines ought to be portable and runnable locally. Number one reason? Give your developers their time (and sanity) back. Pushing to Git in the inner loop disrupts flow and shatters attention. https://www.youtube.com/watch?v=JFnan6s2cDg https://www.youtube.com/watch?v=JFnan6s2cDg
- dosisod 3y ago
  Nice product! I haven't heard of Garden until now. Adding a CLI for Cicada has been on my todo list for a while, and is long overdue! This should be easy enough to do.
- eysi 3y ago
  Another Gardener here :) Just to add to what Tao was saying, our pipelines are not only portable but also "smart". Instead of having to specify every step of a job—either in code or config—you instead tell Garden that it's e.g. a build of type container, or a deploy of type Helm, and our plugin system figures out the rest (of course with escape hatches when needed). We also track the files that go "into" each job and cache the results, so the same job never has to run twice if the code doesn't change. So if you have a large distributed system and a change only affects a small part of it, you don't need to re-run everything. It can save _a lot_ of time. Unrelated, but love that the Cicada team created a Treesitter grammar for Neovim!

deleted 3y ago

[deleted]