I miss Jenkins too. A lot more flexible compared to GitHub Actions.
Also addresses the supply chain attack vector we've seeing recently, by design. You don't pull external dependencies on every CI/CD invocation; they're installed once, on the server. Realised this when I was writing my post on what you have to do to replicate this in a makeshift way in GitHub Actions: https://developerwithacat.com/blog/202604/github-actions-sup...
A GUI that lists all the available options is much more user-friendly than a YAML configuration file where you have to guess them or pore over documentation before starting, but even Jenkinsfile syntax looks better than YAML, and Groovy is a real (edit: realer) language that, in theory, can have things like syntax highlighting and auto-completion.
It's all fun and shells until you start adding parameters especially when those parameters have quotemarks in them. Groovy can get pretty wild with the syntax.
See it how you wish; but shell script execution was part of Jenkins from day 1, to my knowledge, over 20 years ago now. It's a 'workaround' the same way walking upstairs is a workaround for an escalator, imo.
Also addresses the supply chain attack vector we've seeing recently, by design. You don't pull external dependencies on every CI/CD invocation; they're installed once, on the server. Realised this when I was writing my post on what you have to do to replicate this in a makeshift way in GitHub Actions: https://developerwithacat.com/blog/202604/github-actions-sup...