Bullshit, its just another layer of complexity to be managed and that may fail. My guess is that it will take more time maintaining it than it will save you in the majority of cases.
From my experience, this has almost never been the case. Exceptions were when there was infrastructure for the sake of infrastructure.
I have two types of pipelines both based on AWS:
1. Push code to Github -> AWS CodeBuild spins up a prebuilt or custom Docker container (on a server that I don’t have to manage) to build and run unit tests -> Code Deploy agent runs on EC2 instance that runs a script to deploy website.
2. Same as above but Code Deploy runs a CloudFormation template to deploy/update lambdas and other related resources.
The only part of either process that requires me to maintain a server at all is the web server.
It takes me about an hour to set up a new pipeline at the most. It’s basically modified a bunch of yaml/JSON files.
It’s a one time setup that pays dividends through the whole process.
I’ve also used hosted builds with Azure Devops before.