but we have had enough difficulty keeping our CI configuration current based on what cloud provider is falling over this month ;-).
Yes, CI seems to be universally one of those things that is conceptually simple but somehow takes hours and hours to maintain.
Absolutely agreed, glad that it's not only me feeling like that=) If I'd sum up the time I just recently spent on pip, tox, docker, github actions, terraform, .. the list goes on, and compare to time actually spent on coding, it's depressing. for our cloud stuff with Crossbar.io, from code-to-live looks like: GitHub branch (code change) -> GitHub actions (CI main) -> GitHub master (code merge) -> Python wheel (CD "deploy") -> Docker image (CD "docker") -> downstream repo: AMI (via Packer) -> Terraform (live) for devices, it looks like: GitHub branch (code change) -> GitHub actions (CI main) -> GitHub master (code merge) -> Python wheel (CD "deploy") -> snap (CD "snap") -> downstream repo: Yocto -> S3 -> CDN -> RAUC (live) ---- obviously, a lot of things can go wrong. one decision we made: all CI/CD pipelines run through a common set of Python wheels we build.