# Continuous Integration build audit report Continuous Integration build audit report ========================================= Continuous Integration build audit reports provide a real-time report of build events captured during the run of a given build or CloudBees CI Pipeline and is done in a systematic and scalable manner. This report offers the shared services owners and administrators a way to provide auditors with a comprehensive view of the CloudBees CI Pipeline audit trail in a time-saving, automated manner, thus reducing manual effort and error. The build events help trace: * Approvals and approvers * Test results * Generated artifacts * Source control activity You must have a CloudBees Software Delivery Automation license with appropriate capabilities for the **Builds** screen to populate CloudBees CI build summaries and audit reports. For more information, contact your CloudBees sales representative. [](#_accessing_build_summaries)Accessing build summaries -------------------------------------------------------- 1. Select **CD/RO** or **Analytics** from the CloudBees navigation. If **CD/RO** or **Analytics** are not active from the CloudBees navigation, select **Learn more** for licensing information. 2. From the main menu, select **Continuous Integration**. 3. Select **Builds**. ![builds screen](_images/builds.115dc01.png) Figure 1. Builds screen ### [](#_build_details)Build details The following build details are available for each CloudBees CI build. You can filter the builds that are displayed using the **Default filter**, by creating a custom filter, or by using tags. Note that tags are available starting with the CloudBees CD/RO December 2021 Preview release. For details on custom filters, please refer to [Search and filter](/docs/cloudbees-cd/latest/getting-started/search-and-filter). For details on tags, refer to [Create object tags](/docs/cloudbees-cd/latest/objects/object-tagging). * **Title:** The CloudBees CI job and build name. If a display name was defined for the job or build, this is displayed. * **Status:** The current build status: **Running**, **Success**, **Failed**, **Unstable**, or **Not Built**. * **Controller:** The full path to the controller in CloudBees CI. * **Project:** The full project name of the job. If a display name was defined for the job name, this is displayed. * **Start date:** The start date and time for the build. * **Run time:** The total run time for the build, in milliseconds. * **Details:** Once a build has completed, a link to the **Audit report** is available. [](#_accessing_build_audit_reports)Accessing build audit reports ---------------------------------------------------------------- To enable the CloudBees CI build data to appear in this report, in CloudBees CD/RO the **Web Server Host** field in **Administration**  **Server Settings**  **System Settings** must be set with the same hostname that is in the **URL of the CloudBees Software Delivery Automation server** field in CloudBees CI in **Manage Jenkins**  **Configure System**. If the **Web Server Host** field is not set correctly, the build audit report shows a message: "Forbidden: Failed to connect to CI server on ". For details on the **Web Server Host** field, refer to [Server settings - System Settings](/docs/cloudbees-cd/latest/set-up-cdro/server-settings#_system_settings). 1. Select **CD/RO** or **Analytics** from the CloudBees navigation. If **CD/RO** or **Analytics** are not active from the CloudBees navigation, select **Learn more** for licensing information. 2. From the main menu, select **Continuous Integration**. 3. Select **Builds**. ![builds screen](_images/builds.115dc01.png) Figure 2. Builds screen 4. From the **Builds** screen, under **Actions**, select **Details** next to the appropriate CloudBees CI build. The **Build log summary** is displayed. ![summary log screen](_images/summarylogscreen.57e683d.png) Figure 3. Build log summary Use **search** to navigate through the log. 5. Select **Audit reports**. ![Figure 4. Audit report](_images/audit-report.afc4f08.png) Figure 4. Audit report 6. Select an **Audit report** tab for build details. The **Audit report** tabs that are displayed depend on the build type and the plugins that are installed. 7. Optionally, select **Export report** to export the audit report as a PDF file. ### [](#_tests_tab)Tests tab The **Tests** tab reports the test results recorded by the CloudBees CI build, including the total number of tests, passed tests, failed tests, and skipped tests. For any failed tests, the **Test name** and **Run time**, in milliseconds, are displayed. The **Tests** tab appears only if the build archives test results using the [JUnit plugin](/plugins/ci/junit) plugin. ### [](#_source_control_activity_tab)Source control activity tab The **Source control activity** tab reports every source control checkout performed by the build, including the Uniform Resource Identifier (URI) for the source control management tool, and the revision that was checked out. If a previous build of the same job performed a checkout from the same source control tool, a changelog shows all changes between the two builds. Each changelog entry includes the change revision, name of the author, timestamp, and commit message. The **Source control activity** tab appears only if a plugin that implements the `SCM` extension point is installed. The following plugins are supported: * [Git plugin](/plugins/ci/git) * [GitHub Branch Source plugin](/plugins/ci/github-branch-source) * [Bitbucket Branch Source plugin](/plugins/ci/cloudbees-bitbucket-branch-source) * [Subversion plugin](/plugins/ci/subversion) * [Mercurial plugin](/plugins/ci/mercurial) ### [](#_approvals_tab)Approvals tab The Approvals tab reports: * Every CloudBees CI Pipeline input step that has been approved or rejected in the CloudBees CI Pipeline build. If there are no CloudBees CI Pipeline input steps, or it is not a CloudBees CI Pipeline build, the **Approvals** tab is not present. * The Jenkins user ID and email address of the submitter who approved or rejected the input step. * The name of the closest enclosing stage step or parallel branch where the input step occurred in the build. The **Approvals** tab only appears if the [Pipeline: Input Step plugin](/plugins/ci/pipeline-input-step) plugin is used by the CloudBees CI Pipeline. ### [](#_references_tab)References tab The **References** tab reports: * Any associated CloudBees CD/RO Pipelines and releases, with a link to the CloudBees CD/RO Pipeline or release build. These associations can only be created using the [CloudBees CD plugin](/plugins/ci/electricflow) plugin. For successful CloudBees CD/RO Pipeline builds, you can select the **Context menu** to access the **Pipeline run audit report** and **Pipeline run** details. For more information, see [Audit and compliance reports](/docs/cloudbees-cd/latest/audit-reports/) and [View pipeline runs](/docs/cloudbees-cd/latest/pipelines/view-pipeline-runs). * The name and version of any CloudBees CD/RO Pipeline libraries used by the build. These libraries are made available by the [Pipeline: Deprecated Groovy Libraries plugin](/plugins/ci/workflow-cps-global-lib) plugin. ### [](#_artifacts_tab)Artifacts tab The **Artifacts** tab reports: * Every artifact archived with the CloudBees CI build using Jenkins' built-in artifact system, including the artifact, its size in kilobytes, and a link to download the artifact. These artifacts are available by default and no additional plugin is required. * Every artifact the build published to CloudBees CD/RO using the [CloudBees CD plugin](/plugins/ci/electricflow) plugin, including the artifact name, version, and a link to view the artifact in CloudBees CD/RO. ### [](#_plugin_usage_tab)Plugin usage tab The **Plugin usage** tab reports every plugin used by CloudBees CI Pipeline builds, including the plugin artifact ID, plugin display name, version of the plugin installed when the build ran, and a description of plugin usage. The **Plugin usage** tab appears only if the [CloudBees Usage Analyzer Plugin plugin](/plugins/ci/cloudbees-plugin-usage) is installed.