How Different Companies Define Continuous Integration?

Continuous integration is one of the trendy topic in the software industry and getting a lot of attention these days. When you search about it on Google, you get many results and view points.
Let us see some top companies and their view points about ‘Continuous Integration’
1. ThoughtWorks

Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.
By integrating regularly, you can detect errors quickly, and locate them more easily.

Continuous integration is a DevOps software development practice where developers regularly merge their code changes into a central repository, after which automated builds and tests are run. Continuous integration most often refers to the build or integration stage of the software release process and entails both an automation component (e.g. a CI or build service) and a cultural component (e.g. learning to integrate frequently). The key goals of continuous integration are to find and address bugs quicker, improve software quality, and reduce the time it takes to validate and release new software updates.
2. GitHub

Continuous integration can help catch bugs by running your tests automatically. Merge your code with confidence using one of our continuous integration providers.
4. Codeship
Continuous Integration (CI) is a development practice where developers integrate code into a shared repository frequently, preferably several times a day. Each integration can then be verified by an automated build and automated tests. While automated testing is not strictly part of CI it is typically implied.
5. New Relic
The phrase continuous integration (CI) came out of the Extreme Programming process and was one of its original guidelines. Essentially, developers integrate their code into the code repository at least once a day (and preferably more often). Without continuous integration, the odds of one developer’s changes conflicting with another developer’s changes are very high. When long periods of time go by without integration, the problems that surface can be huge and costly to track down and fix.
6. Semaphore

Introducing continuous integration and automated testing into the development process changes the way software is developed from the ground up. It requires effort from all team members, and a cultural shift in the organization.
7. Shippable

Have you been in a situation where multiple code changes have been committed to your application and something then breaks? How do you find out which change caused the problem? Usually, this scenario leads to multiple exchanges with the bug being passed from developer to developer trying to detect where the bug was introduced.Distributed version control systems like Git, while offering many other benefits, have exacerbated the problem by allowing developers to make changes independently to the same pieces of code. The result? Repeated instances of ‘Integration hell’. The most effective way to solve this problem is to catch these bugs as soon as they are introduced. This approach, called Continuous Integration, improves software quality without slowing down releases.
8. CircleCI

Basically, Continuous Integration means multiple developers pushing small, frequent changes to a shared repository or ‘master’. They are integrating changes continuously, rather than periodically, and thus–ta da!–Continuous Integration. There’s a lot out there on CI best practices you can adhere to, but I’d say one of the most important is test all changes that you are making to your code base.
These are the prominent guys in Continuous Integration and have defined the process more or less the same way but what differs is the product, hence you need to try out and see which one better suits your requirements.

