# Continous Integration
[Continuous Integration](https://en.wikipedia.org/wiki/Continuous_integration) (CI) is a development process that requires developers to **integrate** their code into a shared source code repository (git,svn,mercurial,etc) several times a day, while a monitoring process detects code commits and acts upon those commits. Those actions can be the actual checkout of branches, execution of build processes, quality control, and of course our favorite; automated testing.
TestBox can integrate with all major CI servers as all you need to do is be able to execute your test suites and produce reports. You can see that in our [Running Tests](https://testbox.ortusbooks.com/getting-started/running-tests) section and [Reporters](https://testbox.ortusbooks.com/digging-deeper/reporters).
## Benefits of Continuous Integration
* Decrease the feedback loop
* Discover defects faster before production releases
* Developer Accountability
* Increase code visibility and promote communication
* Increase quality control
* Reduce integration issues with other features
* Develop in an Agile/Scrum fashion with continuous improvement
* Much More...
## CI Servers
Here is a listing of some of the major CI servers:
* Jenkins -
* Gitlab -
* Travis -
* Bamboo -
* TeamCity -
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://testbox.ortusbooks.com/digging-deeper/ci.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.