# Jenkins

<div align="left"><img src="https://727226624-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MjFmyReUsbJqDjHEAlW%2F-MjHFgz_NX4gfstfiarj%2F-MjHGVeCfw5CVNYzxkFE%2Fjenkins.png?alt=media&#x26;token=fd711fed-1e29-40a7-af76-0afbd1f6afc2" alt=""></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect Jenkins**

* Find the **Jenkins** integration module under the **CI/CD** section
* Click the **Connect** button
* Enter a Runway-accessible URL to your Jenkins server
* Enter your Jenkins username
* Enter a Jenkins API Token &#x20;
  * You can generate API Tokens within Jenkins by going to `<Jenkins URL>/user/admin/configure` and clicking **Add New Token** in the **API Token** section
* Click **Save**; you’ll be presented with a dialog in which to enter the name of your deployment job/workflows &#x20;
  * The Release Candidate workflow should be the workflow that generates your Release Candidate builds, *i.e.* the builds you use to run Regression testing
  * Optionally, you can also enter the name of a Release job/workflow; *i.e.* the workflow that generates the builds that you end up submitting to the App Store/Play Store

{% hint style="info" %}
Learn more about [builds and branches in Runway](https://docs.runway.team/getting-started/setting-up-your-integrations/builds-and-branches).
{% endhint %}