I think you've missed the most important point about continuous integration. You need to integrate your code regularly with your mainline. The reason why this is so important is it informs you of what the overall state of the codebase. If you have long lived feature branches you will only really know if your work broke something when you merge, instead of when you run the CI on your branch.
Continuous delivery (CD) is more about being able to deploy at any given time. Its not even about your deployment being automated, although automating it is often the most practical thing to do. I suspect the reason for people getting this wrong so often is because of vendors trying to push their products on blogs...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think you've missed the most important point about continuous integration. You need to integrate your code regularly with your mainline. The reason why this is so important is it informs you of what the overall state of the codebase. If you have long lived feature branches you will only really know if your work broke something when you merge, instead of when you run the CI on your branch.
Continuous delivery (CD) is more about being able to deploy at any given time. Its not even about your deployment being automated, although automating it is often the most practical thing to do. I suspect the reason for people getting this wrong so often is because of vendors trying to push their products on blogs...