> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/orchestration-module-opsmx-enterprise-for-spinnaker-oes/additional-feature-configuration/add-ci-system/overview-and-compatible-list-of-ci-systems-by-spinnaker.md).

# Overview and Compatible List of CI Systems by Spinnaker

## Steps to Add Continuous Integration to Spinnaker <a href="#steps-to-add-continuous-integration-to-spinnaker" id="steps-to-add-continuous-integration-to-spinnaker"></a>

### Continuous Integration Overview and Importance <a href="#continuous-integration-overview-and-importance" id="continuous-integration-overview-and-importance"></a>

* Continuous Integration (CI) is the process of automating the build and testing of code every time a team member commits changes to version control.
* CI encourages developers to share their code and unit tests by merging their changes into a shared version control repository after every small task completion.
* In Spinnaker, CI can listen to events, and collect artifacts by builds from Continuous Integration (CI) systems. These can trigger pipelines, and the same artifacts can be used by image bakery to produce images of the machines.

### Spinnaker Supported CI Systems <a href="#spinnaker-supported-ci-systems" id="spinnaker-supported-ci-systems"></a>

* Following are the list of CI systems, supported by Spinnaker currently
  1. Google Cloud Build
  2. Jenkins
  3. Travis CI
  4. Wercker


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/orchestration-module-opsmx-enterprise-for-spinnaker-oes/additional-feature-configuration/add-ci-system/overview-and-compatible-list-of-ci-systems-by-spinnaker.md?ask=<question>
```

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.