We are _besieged_ by caching issues. A good 1/4 to 1/3 of a particular AMI build action we run will fail because of a package mirror at GH being out of date.
Looks like an area ripe for disruption! (Only half-joking.)
It seems like there's enough disruption in this area already.
I think a hosted mulit-tenant CI platform appears fairly simple on the surface, but there's actually a lot of complexity under the hood when your product is arbitrary code execution as-a-service - and you want to offer a smoother user experience than something as general-purpose as a container runtime.
Especially when you throw in a large and generous free tier.
None of the recent examples of unbundled multi-tenant CI/CD appear to have wildly successful exit stories, or even continuing to run with great growth and profitability stories. I’m thinking of companies like Travis with that comment (which was, IMO, delightful to use for its era). It’s probably pretty hard to sell this to the average enterprise when you’re competing against product suites which do 100x more? Definitely feels like a situation where those suites are “Jack of all trades, and master of none” though, and collectively mediocre vs. individually excellent.