I'll think twice before using GitHub Actions again

Re:I'll think twice before using GitHub Actions again by rtpg on Monday January 20, 2025 @06:40PM (#42774521)

The actual subtle issue here is that sometimes you actually need CI features around caching and the like, so you are forced to engage with the format a bit.

You can, of course, chew it down to a bare minimum. But I really wish more CI systems would just show up with "you configure us with scripts" instead of the "declarative" nonsense.

[ Parent | on HN ]

Re:I'll think twice before using GitHub Actions again by Guvante on Monday January 20, 2025 @06:47PM (#42774580)

CI that isn't running on your servers wants very deep understanding of how your process works so they can minimize their costs (this is true whether or not you pay for using CI)

[ Parent | on HN ]

Re:I'll think twice before using GitHub Actions again by rtpg on Monday January 20, 2025 @08:04PM (#42775139)

Totally! It's a legitimate thing! I just wish that I had more tools for dynamically providing this information to CI so that it could work better but I could also write relatively general tooling with a general purpose language.

The ideal for me is (this is very silly and glib and a total category error) LSP but for CI. Tooling that is relatively normalized, letting me (for example) have a pytest plugin that "does sharding" cleanly across multiple CI operators.

There's some stuff and conventions already of course, but in particular caching and spinning up jobs dynamically are still not there.

[ Parent | on HN ]