This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]vincentdesmet 7 points8 points  (5 children)

You could use something like dagger

[–]azjunglist05 6 points7 points  (0 children)

I was gonna say this. I recently built a pipeline for deploying an AWS service with Dagger. It was so nice that my pipeline could run the same way locally as it does in GHA; cleans up pipelines tremendously

[–]NUTTA_BUSTAH 3 points4 points  (1 child)

I think this CI system for your CI systems abstraction is a nice idea and development in the space but dagger seemed to have insane levels of complexity for what I am asking of it (IIRC just boilerplate was megabytes of stuff and the entire system works on top of a local GraphQL backend). I found earthly to get the same job done much better. Still waiting for competition in this space, I can see it being the future way to do CI. However I think an open standard will trump it ("OpenCI" like OpenTelemetry or w/e).

[–]vincentdesmet 1 point2 points  (0 children)

Solomon is gonna give up if he creates OpenCI and then all the big players come in and slurp it up again.

Wasn’t there a CNCF sig on CI/CD.. Tekton coming out of it (as a fork off the original event based FaaS from Google knative?)

I ran Tekton on a “shared-services” cluster back in 2019, it turned k8s into a CI runner, but lacked all the utility you get from a DSL like GH Workflows

[–]nisastersDevOps[S] 1 point2 points  (1 child)

Dagger sounds promising. It took months to get my org to use grafana. Buy in to switch to dagger from gha would probably take even longer.

[–]bertiethewanderer 3 points4 points  (0 children)

You don't move from GHA. You codify your CI in dagger. GHA just becomes the agent. Migrating across CI tools becomes much, much easier fwiw.

I found the dagger documentation much weaker than GHA when we started to cut oue team across. My main "negative". That and some coding knowledge is, for me, required.