How to distinguish between the concepts of DevOps and Continuous Integration?

Question

Continuous Integration

I can not distinguish between the concepts of DevOps and Continuous Integration. It seems that in some ways they are similar, and at the same time, DevOps is clearly wider.
Is CI fully included in the concept of DevOps, or is there something in its content that goes beyond DevOps?
When it comes to the infrastructure of a development company (or department), where does continuous integration end and other DevOps functions in the product-customer-service chain begin?

Answer 1

DevOps is really a broader concept.
It includes:
1. Code lifecycle management (Continuous Integration, Continuous Testing, Continuous Deployment, Continuous Delivery)
2. Finding/correcting bottlenecks in the work and interaction of architects/developers/testers/sysadmins.
3. Development of a release policy: how and why branches are branched (very dependent on the type of VCS), how branches are merged, how branches are named, how branch names are used in CI/CD.
4. Tracking / "paying off" technical debt (in practice, this task is taken over by the team leader or, more often, by no one at all).
Maybe someone else will add something.
___
2* - there are a lot of managerial things here. For example, a developer needs logs. He worries the sysadmin, he makes him wait, then "unloads" the context of his task from his head, downloads and forwards the logs, then both spend time procrastinating in the process of entering back into the contexts of their tasks = 20 min.
DevOps = come and deliver a self-service service to them. In this case, a log collection service available to the developer. The developer instantly looks at the log = 1 min. The system administrator is not in the know and continues to work on his task.