I've been on such teams. Usually it was championed by some devops who just cared a lot about it and was willing to put in a lot of work to make it happen. It's

I've been on such teams. Usually it was championed by some devops who just cared a lot about it and was willing to put in a lot of work to make it happen. It's not all that great though. I'd say that, since it's usually maintained by devops guys, it's not fully designed with developers in mind. For example, the deployment to a CI is usually unacceptably slow for at least one seeminlgy unfixable reason (or perhaps the devops don't care enough, because the slowness doesn't hurt them as much). So, in practice, the CI is only used to run the automated test suite before the final OK on the merge and before that, you're better off running and testing things manually.