Re:GitHub Actions is slowly killing engineering teams
by tcoff91 on Friday February 06, 2026 @12:38AM
(#46909508)
Jenkins had a lot of issues and I’m glad to not be using it overall, but I did like defining pipelines in Groovy and I’ll take Groovy over YAML all day.
[ Parent
| on HN ]
Re:GitHub Actions is slowly killing engineering teams
by bigstrat2003 on Friday February 06, 2026 @01:17AM
(#46909701)
Jenkins, like many complex tools, is as good or bad as you make it. My last two employers had rock solid Jenkins environments because they were set up as close to vanilla as possible.
But yes, Groovy is a much better language for defining pipelines than YAML. Honestly pretty much any programming language at all is better than YAML. YAML is fine for config files, but not for something as complex as defining a CI pipeline.
Re:GitHub Actions is slowly killing engineering teams
by PunchyHamster on Friday February 06, 2026 @03:51AM
(#46910542)
biggest flaw of jenkins is that by default it runs on builder env, as it was made pre-container era. But I do like integration with viewing tests and benchmarks directly in the project, stuff that most CI/CD systems lack