Sounds like you have the same pain points as everyone else; you're just more willing to ignore them.
I am with the author - we can do better than the status quo!
I am with the author - we can do better than the status quo!
I commit code, push it, wait 45 seconds, it syncs to AWS, then all my sites periodically ping the S3 bucket for any changes, and download any new items. It's one of the most reliable pieces of my entire stack. It's comically consistent, compared to anything I try building for a mobile app or pushing to a mobile app store.
I look forward to opening my IDE to push code to the Actions for my web app, and I dread the build pipeline for a mobile app.
Well yeah because nobody is saying it isn't reliable. It's the setup stage that is painful. Once you've done it you can just leave it mostly.
I guess if your CI is very simple and always the same you are exposed to these issues less.
I would recommend looking at Fastlane[0] if you haven't already.
You notice a deprecation warning in the logs, or an email from GitHub and you make a 1 line commit to bump the node version. Easy.
Sure you can make typos that you don’t spot until you’ve pushed and the action doesn’t run, but I quickly learned to stop being lazy and actually think about what I’m writing, and get someone else to do an actual review (not just scroll down and up and give it a LGTM).
My experience is same as the commenter above, it’s relatively set and forget. A few minutes setup work for hours and hours of benefit over years of builds.
It's how it works now. It doesn't have to forever. We can imagine a future in which it works in a better way. One that isn't so annoying.
> I don't think there's some universally perfect solution that magically just works all the time and never needs intervention or updating.
Again you seem to be confused as to what the issue is. Maintenance is not painful. Initial development is.