> 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.10/orchestration-module-opsmx-enterprise-for-spinnaker-oes/additional-feature-configuration/add-ci-system/steps-to-configure-ci-systems/wercker.md).

# Wercker

{% hint style="info" %}
This is an older version of the document. To view the most recent version of the document, click [here](https://docs.opsmx.com/products/orchestration-module-opsmx-enterprise-for-spinnaker-oes/additional-feature-configuration/add-ci-system/steps-to-configure-ci-systems/wercker).
{% endhint %}

## Steps to Setup Wercker for Spinnaker <a href="#steps-to-setup-wercker-for-spinnaker" id="steps-to-setup-wercker-for-spinnaker"></a>

* This is a tool that empowers organizations and their development teams to achieve continuous integration and continuous delivery (CI/CD) goals with micro-services and Docker.
* Using Wercker as a CI system, can enable within Spinnaker as a pipeline trigger and also as a pipeline stage.

### Prerequisites: <a href="#prerequisites" id="prerequisites"></a>

* To enable Wercker integration in Spinnaker, you will need to have:
  1. A login to Wercker, which can be set up [here](https://app.wercker.com/).
  2. A Wercker “personal token” to provide to Spinnaker so that it can access the Wercker API on your behalf. Personal tokens [can be generated](https://devcenter.wercker.com/development/api/authentication/) on Wercker by logging in andvisiting your “Settings” page.

### Enable Wercker Master to Spinnaker using Halyard: <a href="#enable-wercker-master-to-spinnaker-using-halyard" id="enable-wercker-master-to-spinnaker-using-halyard"></a>

* Without “master” it’s not possible for connectivity between Wercker and Spinnaker. This also consists of Wercker URL and credentials

  1.Ensure to have Wercker CI is enabled on Spinnaker, by executing the below command

  ```
      hal config ci wercker enable
  ```

  2.Execute the below command to enable Stage feature on Wercker

  ```
      hal config features edit --wercker true
  ```

  3.For connection between Wercker and Spinnaker, add a Wercker master

  ```
      hal config ci wercker master add mywercker1
      --address https://app.wercker.com/
      --user myuserid
      --token
  ```

  4.To Invoke above changes, re-deploy Spinnaker

  ```
      hal deploy apply
  ```


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.10/orchestration-module-opsmx-enterprise-for-spinnaker-oes/additional-feature-configuration/add-ci-system/steps-to-configure-ci-systems/wercker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.