onlinepersona@programming.dev
on 03 Oct 2023 22:31
nextcollapse
Makes me think of dagger.io (why can’t techies come up with names outside of a dictionary?)
BeanCounter@sh.itjust.works
on 04 Oct 2023 00:06
nextcollapse
Because if they try, you get gems like XÆA-12
odium@programming.dev
on 04 Oct 2023 15:07
collapse
You do get some pretty good names like Netflix, roomba, Skype, etc.
thesmokingman@programming.dev
on 04 Oct 2023 00:34
collapse
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.
taaz@biglemmowski.win
on 03 Oct 2023 23:19
nextcollapse
snowe@programming.dev
on 04 Oct 2023 04:28
collapse
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.
Knusper@feddit.de
on 04 Oct 2023 05:23
nextcollapse
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.
Die4Ever@programming.dev
on 04 Oct 2023 05:26
collapse
Yeah I need to start doing this more lol
worldofgeese@lemmy.world
on 04 Oct 2023 06:46
collapse
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 github.com/garden-io/garden
threaded - newest
Makes me think of dagger.io (why can’t techies come up with names outside of a dictionary?)
Because if they try, you get gems like XÆA-12
You do get some pretty good names like Netflix, roomba, Skype, etc.
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.
github.com/nektos/act
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.
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.
Yeah I need to start doing this more lol
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 github.com/garden-io/garden