New ask Hacker News story: Ask HN: How can we make the current CI/CD ecosystem better?

Ask HN: How can we make the current CI/CD ecosystem better?
2 by dosisod | 0 comments on Hacker News.
Having dealt with lots of CI/CD platforms (GitHub Actions, Gitlab CI, Azure DevOps, etc.), I feel like there is lots of room for improvement: * There is little to no inter-op between CI providers. Sure there are 3rd party providers, but they only seem to focus on the basics, like running a job when a commit is pushed. But, if you choose something like GitHub Actions, you are now locked into their platform, making switching Git hosting providers very painful. * YAML. Everything is YAML. Sometimes it is just one big file (Gitlab, Travis, CircleCI, etc), and it becomes very hard to maintain very quickly. Workflows for GitHub Actions can be split up into different files, but at the end of the day, you are still writing YAML, which means no loops, conditionals, functions, and so forth. In addition, you must follow a strict file structure, meaning very little room for customization. In many cases, you need to write a Makefile/Python/shell script for more complex situations. Does anyone else share these annoyances? Are there any similar sorts of issues that you deal with on a day to day basis that you wish could be improved?