5 ms·

This is a compelling testimonial. Someone recently posted a 'git ops' package here that was equally simple and bash based. Im interested to try, but im wonderin

This is a compelling testimonial. Someone recently posted a 'git ops' package here that was equally simple and bash based. Im interested to try, but im wondering what the rationale will be for avoiding github actions. If you could share script or snippets I would be grateful. One difficulty for me is my datastore and reporo g package is a python application using Prefect, and I manage dependency with Poetry. The 'poetry install' phase isnt always ha ds off and my script fails.

ambicapter 2y ago
> but im wondering what the rationale will be for avoiding github actions. Having used them, I would say lack of test-ability and slightly unhelpful flow-control rules would be my guess. The former you'll find in any managed CI solution.
kerkeslager 2y ago
> Im interested to try, but im wondering what the rationale will be for avoiding github actions. I don't. Github actions are simple enough, and easily run the scripts I'm talking about. > If you could share script or snippets I would be grateful. Maybe I'll pull something together and post it if I get the chance this week. > One difficulty for me is my datastore and reporo g package is a python application using Prefect, and I manage dependency with Poetry. > The 'poetry install' phase isnt always ha ds off and my script fails. I don't use poetry, I use pypi directly with pip, so not sure I can help you there. That sounds like a problem to debug. But notably, it's probably easier to debug than similar problems with a containerized system (which happen).