CI Job History

The CI Job History page offers a consolidated overview of all CI jobs executed to date. In addition to listing previously triggered jobs, it provides various job-level actions and insights. Once a build is completed, jobs can be re-triggered directly from this interface. Users can monitor job statuses, review detailed deployment outcomes, and access build logs, all from a single, centralized location.

Step-By-Step Guide:

  1. Click on the "CI Job History" option on the left side navigation pane to access the "CI Job History" page

  2. Use the search fields—Job name, Build number, and Build label—to quickly locate specific CI Jobs within the CI Job History page.

  3. Use the Filters option to narrow down job history results by date, build status, deploy status, commit status, and triggered user.

  4. The Columns option enables customization of the CI Job History table view by selecting or deselecting specific fields for display.

  5. Clicking the Deployment Queue button displays a prioritized list of CI jobs lined up for deployment. Jobs are executed sequentially from top to bottom based on this order.

  6. Commit Queue The Commit Queue allows users to view and manage jobs awaiting commit execution. Jobs are processed top to bottom based on their order of priority.

  7. The CI Job History table displays key details such as:

    1. Job name: Displays the name assigned to each CI Job for identification.

    2. Time of build: Shows the exact date and time when the build was executed.

    3. Build number: Indicates the sequential number assigned to each build of a CI Job.

    4. Build label: Represents a custom label associated with the build.

    5. Build status: Reflects whether the build was successful or failed using visual indicators.

    6. Deploy status: Displays the status of the deployment for the job.

    7. Commit status: Shows the success or failure of any commit operations tied to the job.

    8. Post-deploy status: Indicates the outcome of post-deployment activities, if configured.

    9. Actions: Offers options to re-trigger the job or access additional actions via the menu.

  8. Triggering a CI Job Build from History

    • Build Job (Play icon): Click the play icon under the Actions column to initiate a build for the selected CI job directly from the history list.

    Build Inputs Panel

    • Build Label: Enter a unique identifier to label the new build for tracking purposes.

    • Build Comment: Provide optional context or notes describing the intent or changes in this build.

    • Deployment Type: Choose from "Commit and deploy", "Deploy only", or "Commit only" based on the action needed.

    • Enable Rollback for this Build: If this option is selected during the job creation, the same state will reflect while job gets triggered.

    • Build Notes: Add additional information or annotations relevant to the build; this field is optional.

    • Trigger Build Button: Click this button to finalize and initiate the CI job build with the provided inputs

  9. Accessing the Build List from CI Job History

    In the CI Job History interface, each row represents an individual CI Job entry with various associated actions. To access detailed build information for any CI Job:

    1. Build List Navigation: Click the ellipsis icon (â‹®) under the Actions column for the desired CI Job. From the context menu that appears, select Build List. This action navigates to the CI Job Builds screen specific to that CI Job.

    1. CI Job Builds Overview: The CI Job Builds screen presents a tabular list of all builds triggered for the selected job. The following attributes are displayed for each build:

      • Build Number: Sequential identifier for each build.

      • Build Name: Descriptive label assigned to the build.

      • Triggered Date and Triggered By: Timestamp and initiator of the build.

      • Commit ID: The unique identifier of the commit associated with the build.

      • Build Status, Deploy Status, Commit Status, and Post Deploy Status: Visual indicators reflecting the outcome of each stage.

    The following explains the options available under the actions of the "CI Job Builds" section:

    • Build Results: Displays the overall outcome and statistics of the build process.

    • Post Deploy Results: Shows results of deployment validation post-build.

    • Build Info: Provides basic metadata and configuration details of the build.

    • Build Changes: Lists all the changes included in the selected build.

    • Commit Log: Displays the sequence of commits associated with the build.

    • Commit Revision Log: Shows a list of modified files and their actions in the commit.

    • Commit File Diff: Presents a visual comparison of changes between file versions.

    • Rollback: Initiates a rollback of the build deployment from the target org.

    • Download Build Backup Snapshot: Allows you to download a backup archive of the build snapshot.

  10. Viewing Build Results: Within the CI Job History screen, click the ellipsis icon corresponding to a specific job entry. Select Build Results from the dropdown to view the execution details of that build, including logs, errors (if any), and success metrics.

    1. The features that are part of the build can be downloaded using the download option

    2. The "logs" of the feature deployment can be observed by clicking on the "View Logs" option available

  11. Accessing Post-Deployment Details from the CI Job History Page

    To review the logs of post-deployment activities for completed CI jobs:

    1. Navigate to the CI Job History page and locate the job of interest.

    2. Open the Actions menu (represented by the vertical ellipsis â‹®) corresponding to the selected build.

    3. Choose the Post Deploy Results option from the dropdown.

    1. This action opens the Feature Details panel that provides build and deployment status specific to each post-deploy Org configured in the CI Job.

      Viewing Deployment Logs of Post-Deploy Orgs Within the Feature Details panel:

      • Select the desired Post Deploy Org from the dropdown at the top-left to filter logs specific to that target Org.

      • Click the View Logs icon adjacent to the desired feature to open detailed deployment logs.

      The Feature Logs panel then displays the Deploy Log, outlining each deployment step executed on the selected post-deploy Org, including:

Point to Note:

  1. Post-deployment activities support up to a maximum of five Salesforce Orgs. When multiple Orgs are selected, these activities are executed sequentially—the process moves to the next Org only after the current one completes.

  2. Detailed success or failure records for individual objects are available only if post-deployment activities are completed successfully across all selected Orgs.

  1. Build Info

    The Build Info option from the CI Job History menu opens a panel displaying metadata for the selected build, including job name, build number, status details, deployment target, and initiator. This summary provides a consolidated view of critical build-level attributes.

  2. Build Changes – CI Jobs History

    The Build Changes view, accessible from the contextual menu in the CI Jobs History screen, provides a breakdown of metadata components included in a specific CI job build.

    Upon selecting Build Changes, a categorized list of changes is displayed, grouped by metadata categories. Within each category, individual metadata components are listed.

    This helps track the exact metadata items that were part of a specific build, aiding in review, troubleshooting, and audit purposes. A download icon is also available to export this information.

  3. Commit Log – Step-wise Execution Breakdown

    Accessing the Commit Log from the contextual menu on the CI Jobs History screen opens a detailed breakdown of the step-wise execution performed during the commit process. The log provides a vertical list of steps such as Checkout, Sorting Structure, Diff, Converting Structure, Commit, and Delta.

    Each step is expandable and includes messages logged in real time, offering complete transparency into how the commit execution was handled.

  4. Commit Revision Log

    The Commit Revision Log from the CI Jobs History contextual menu opens a panel listing all the files included in the commit, along with their actions—Modified (M) or Deleted (D). Each entry in the log provides the full file path, aiding traceability and audit for changes made in the build.

  5. Commit File Diff – CI Job History

    From the CI Jobs History page, selecting the Commit File Diff option from a job’s action menu displays the detailed file-level changes grouped under categories like Data and Filters.

    1. In the Data tab, files are listed with summary stats for additions and deletions, and expanding a file reveals a side-by-side JSON diff view with highlighted insertions and removals.

    1. The Filters tab shows query-based changes in JSON format, such as added filter logic or metadata.

  6. Rollback

    On the CI Jobs History page, the rollback operation is accessed via the contextual menu in the Actions column by selecting the Rollback option.

    This opens the Feature Deployment Rollback dialog, where the user first chooses the org(s) to roll back from under the Rollback From dropdown.

    Following this, one or more deployed templates can be selected using the Rollback Deployed Template(s) dropdown. After the necessary selections are made, the rollback is initiated by clicking the Rollback button.

  7. Download Build Backup Snapshot

    The Download Build Backup Snapshot option in the CI Jobs History page allows downloading a backup of the selected build for archival or restoration purposes.

Last updated

Was this helpful?