# Triggering Builds for your CI Job

{% hint style="info" %}
The **CI JOBS** screen is best viewed when the zoom setting is set to **80%** on your chrome/firefox browser.
{% endhint %}

### Overview <a href="#overview" id="overview"></a>

The following articles describe how to trigger a new build for your CI Job created in AutoRABIT.

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

* Users must have permission to access the **CI Job Results** page.
* The account owner or admin can assign this permission under **Admin > Roles** by enabling the required permission in the role configuration.

***

### Trigger a new Build <a href="#trigger-a-new-build" id="trigger-a-new-build"></a>

1. Navigate to the **CI Job Results** screen.
2. This screen lists all CI Jobs for which builds have been triggered.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FRwWnx0lGrfK5Vuj7SFZl%2Fimage.png?alt=media&#x26;token=5e177e74-21d6-40d7-9c24-6fa966ee4785" alt="CI Job Results screen with build history"><figcaption></figcaption></figure>

3. Jobs with deployments display the icon: ![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FEpUe8oSZdWHxRLlo7Ym6%2Fimage.png?alt=media\&token=356e26f9-ed9b-4c84-99ce-d239adc23912), while validated-only jobs show: ![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FnUXMFaV0zb0WmJHfdige%2Fimage.png?alt=media\&token=a78baeb9-69b6-424d-9d1b-f50b9e07dbb5)
4. Use the **Select Job** dropdown to choose your CI job.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FVDdfszT3tvoN0rnurMuY%2Fimage.png?alt=media&#x26;token=2d656f35-8f2a-4d13-8826-9224dd242cc0" alt="Select CI Job from dropdown list" width="427"><figcaption></figcaption></figure>

5. If no builds exist yet, you'll see:\
   \&#xNAN;**"No builds found for this job. Please trigger a new build for results."**\
   Click **Build Now**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FRWigCLGr7a3eOeylJO8V%2Fimage.png?alt=media&#x26;token=1b9dc948-6016-4728-8bd1-56fb95261bbe" alt="Build Now button for first-time build trigger"><figcaption></figcaption></figure>

6. If previous builds exist, click **Build Now** to trigger a new build.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FmiMfO20eYlJTqzbItC7p%2Fimage.png?alt=media&#x26;token=a6e8834d-da9a-4f9d-a263-b7a6ace84e23" alt="Build Now button to trigger additional builds"><figcaption></figcaption></figure>

7. The build initiation screen will differ depending on whether your CI Job is configured with ALM.

***

**ALM-configured CI Job**

ALM-integrated CI Jobs display ALM work item information from the source version control branch.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FJIjW1jQkKplqI5L7UFez%2Fimage.png?alt=media&#x26;token=41b01505-5193-4b3f-9322-0a5dd1da2df7" alt="ALM integration panel showing work items"><figcaption></figcaption></figure>

* **Commit**: Displays work items committed to the source branch.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FW6ppHruVuUr5bPBKIJ8P%2Fimage.png?alt=media&#x26;token=7e5ba094-1509-49f6-a81b-7c05ff3c6cb0" alt="ALM work items from commits" width="513"><figcaption></figcaption></figure>

* **Merge**: Displays work items merged into the source branch.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FVKy3IpImUq79RceM1RAA%2Fimage.png?alt=media&#x26;token=1b8864a4-25d5-4277-a313-4c8b4af1c5dc" alt="ALM work items from merges" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Important Note:**

1. **ALM Label Type: Commit** — If a label is selected, results show all commits regardless of status.
2. If no label is selected, all committed and merged revisions matching the CI Job configuration will be packaged. This applies to scheduled CI Jobs as well.
   {% endhint %}

***

**Without ALM-configured CI Job**

CI Jobs without ALM integration show the following build input screen:

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fjbq8OHAf2YwuaZpl7IjC%2Fimage.png?alt=media&#x26;token=6d2a4c0e-c7bf-48cf-b69a-6bd6057b84b0" alt="Trigger build screen for non-ALM jobs"><figcaption></figcaption></figure>

* Enter a **Title** and optional **Comments**
* Choose **Deployment Type**:
  * **Deploy**: Executes a full deployment to destination org or branch
  * **Validate only**: Runs validations without deployment

**Additional Options:**

1. **Run Code Coverage On Destination**
   * Enabled if test execution is configured in the CI Job
   * Generates Apex test coverage reports
2. **Enable Rollback For Deployment**
   * Enabled if **Rollback** was selected in the CI Job's **Deploy** section
3. **Ignore Warnings**
   * Allows deployment to continue despite warnings

* Use the **Notes** field to enter optional information
* Click **Trigger Build** to validate and execute the build

{% hint style="info" %}
**Important Notes:**

* The **Validate only** deployment type does not run test cases.
* Avoid editing CI Jobs while a build is in progress to prevent job failure. Abort the build if edits are necessary.
  {% endhint %}

8. Upon triggering, you will be redirected to the [CI Job Results](https://knowledgebase.autorabit.com/~/revisions/2pZloeAS2TMhsiKyUhoF/product-guides/arm/arm-features/automation-and-ci/ci-job-history) page, where build reports are available.

***

### For the following Pull Request events, AutoRABIT triggers a build:

**Validation Details:**

* Editing and committing a pull request triggers the CI job as expected.
* When a pull request is edited, GitHub marks it accordingly, and AutoRABIT builds are triggered upon commit synchronization.

**Webhook Delivery Screenshot:**

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FOMDk3DRPftxXJQGNf0d2%2Fimage.png?alt=media&#x26;token=1b475892-8474-4a50-895f-ac5dce7f25cc" alt="Webhook event delivery log from GitHub"><figcaption></figcaption></figure>

**Webhook Configuration Screenshot:**

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FJvYpfC9YJHhrQEKm603U%2Fimage.png?alt=media&#x26;token=af29462c-1cee-47bb-a90b-5fd73074be69" alt="Webhook settings for GitHub repository integration"><figcaption></figcaption></figure>
