> For the complete documentation index, see [llms.txt](https://testbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://testbox.ortusbooks.com/digging-deeper/ci.md).
# 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](/getting-started/running-tests.md) section and [Reporters](/digging-deeper/reporters.md).
## 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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://testbox.ortusbooks.com/digging-deeper/ci.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.