> I'll go rather go back to paper than to just move every last bit of my companies data into the hands of a single company (looking at you, Microsoft).
To me, given he critical importance of a working CICD, it feels like Microsoft controlling both GitHub Actions and Azure Pipelines poses a significant risk of having the proverbial rug pulled from under you. I don't expect Microsoft to invest on GitHub Actions enough to make them the clear winner in UX and cost, for example. Both Azure Pipelines and GitHub Actions are appallingly bad in UX, at least compared to GitLab CICD or even CircleCI or Travis, and I don't expect to turn that around due to their incentives to not make either one too competitive regarding the other in-house service. But that's just me.
The two best CI tools I've ever seen were Gitlab, as its approch was just working good (tm) and Teamcity, as its approach with the UI & Kotlin integration was just nice.
Then I've seen Azure Pipelines, which seem like an unfinished product because it competes with Github Actions, and then there is Github Actions which seem to come from someonw who loves to write k8s yml files (they do what they do, but they're unreadable).
Not GitHub Actions but Azure Pipelines: The sheer endlessness of logs, even for the smallest tasks there are hundreds of lines of logs, and it's nearly impossible to find the line you need if something went wrong.
To me, given he critical importance of a working CICD, it feels like Microsoft controlling both GitHub Actions and Azure Pipelines poses a significant risk of having the proverbial rug pulled from under you. I don't expect Microsoft to invest on GitHub Actions enough to make them the clear winner in UX and cost, for example. Both Azure Pipelines and GitHub Actions are appallingly bad in UX, at least compared to GitLab CICD or even CircleCI or Travis, and I don't expect to turn that around due to their incentives to not make either one too competitive regarding the other in-house service. But that's just me.