Anyone have experience in Dagger here, or similar? The premise of standardizing how CI/CD pipelines get written, without having to run everything in the actual CI pipeline would be a nice step forward - vs today we don't "really" knowing if CI will pass until after we've pushed to the remote. https://blog.logrocket.com/using-dagger-with-docker-for-better-ci-cd/#what-dagger

Related: https://github.com/nektos/act

@Will Da Silva (Arch) do you use

act

for local development? I took a look at it a while back but had a tough time getting results and output 1:1 with GitHub. I didn't spend a huge amount of time configuring though.

I do not. Just figured it'd be worth sharing since in theory it should let us run the workflows locally without rewriting them.

@Will Da Silva (Arch) - Thanks for sharing

act

. I tried one of these a while back (I don't remember the name) and had a not-great experience; didn't get far and decided it wasn't worth the extra layer. I'm still curious about the concept though.

I gave dagger a quick try last week after learning about it in a newsletter. I was able to run

meltano --version

with small changes to the most basic example using the official meltano image. It probably is better for apps that are meant to run in a specific environment (e.g. Ubuntu 20.04) rather than supporting multiple OSs or distributions.

Has anyone here tried https://github.com/mxschmitt/action-tmate? It lets you SSH into a GitHub runner. I may try it out next time I'm struggling to reproduce an issue locally.