Triggering Builds for your CI Job
Overview
The following articles describe how to trigger a new build for your CI Job created in AutoRABIT.
Prerequisites
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
Navigate to the CI Job Results screen.
This screen lists all CI Jobs for which builds have been triggered.

Jobs with deployments display the icon:
, while validated-only jobs show:
Use the Select Job dropdown to choose your CI job.

If no builds exist yet, you'll see: "No builds found for this job. Please trigger a new build for results." Click Build Now.

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

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.

Commit: Displays work items committed to the source branch.

Merge: Displays work items merged into the source branch.

Without ALM-configured CI Job
CI Jobs without ALM integration show the following build input screen:

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:
Run Code Coverage On Destination
Enabled if test execution is configured in the CI Job
Generates Apex test coverage reports
Enable Rollback For Deployment
Enabled if Rollback was selected in the CI Job's Deploy section
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
Upon triggering, you will be redirected to the CI Job Results 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:

Webhook Configuration Screenshot:

Last updated
Was this helpful?