Triggering Builds for your CI Job

The CI JOBS screen is best viewed when the zoom setting is set to 80% on your chrome/firefox browser.

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

  1. Navigate to the CI Job Results screen.

  2. This screen lists all CI Jobs for which builds have been triggered.

CI Job Results screen with build history

  1. Jobs with deployments display the icon: , while validated-only jobs show:

  2. Use the Select Job dropdown to choose your CI job.

Select CI Job from dropdown list

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

Build Now button for first-time build trigger

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

Build Now button to trigger additional builds

  1. 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.

ALM integration panel showing work items

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

ALM work items from commits

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

ALM work items from merges

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.

Without ALM-configured CI Job

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

Trigger build screen for non-ALM jobs

  • 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

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.

  1. 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 event delivery log from GitHub

Webhook Configuration Screenshot:

Webhook settings for GitHub repository integration
PreviousInstall an Unlocked Package from Version Control BranchNextCI Job History

Last updated

Was this helpful?