View chain runs

Open a chain to examine each chain run in detail, and view plugin findings and measurements. For chains with dependencies, you can also view information about discovered vulnerabilities.

To view the chain run results:

  1. From the spaces list at the top right, select a space.
  2. On the Products page, open a product or Git repository.

  3. In the sidebar, select Chains.

  4. In the chains list, click a chain's name to open the chain.

    A list of the chain's recent runs is displayed. Each run shows:

    • The run's state, indicated by an icon.

    • The chain run build number.

    • The changeset where the chain ran.

    • The duration of the run.

    • The user that ran the chain.

    • The instance of PulseUno that ran the chain.

  5. To view the history of changes made to the chain, click Edit. In the chain's editing window, select the History tab. You can filter history by date, user, property, or child entities.

    When finished, click Close to return to the list of chain runs.

  6. To inspect the details of a chain run, click the chain run link. On the chain run page, navigate between the tabs to view chain information:

    Tab Description
    Logs

    Displays the output log for each plugin step in the chain. For steps that ran other chains, includes links to child chain runs.

    Note: For a chain that is currently running, the Logs tab displays the progress of the remaining steps.

    The state of each chain step is indicated by an icon. For details, see Chain run states.

    To download the chain run log, click Download Logs at the top right. Log files use LF line separators.

    To open the log for a plugin step, click the plugin step. Warnings and messages in the log are color-coded.

    To filter the information in the plugin step log, select a log threshold level. Typically, the log is set to the Info level, which includes general information, warnings, and errors.

    Findings Displays a view of findings for each plugin in the chain. Findings are grouped by type such as Errors, Warnings, Failures, and Information. Provides the path to each file with findings.
    Measurements

    Displays the measurements for each plugin in the chain, including the measurement count, finding count, and execution time.

    The chain run state for each chain step is indicated with an icon.
    Tests

    Displays the results of tests triggered by the chain. For some plugins, includes report files that you can view and download.

    You can sort and filter the list of tests. For example, select to display only failed tests.

    If the chain ran no tests, the tab is not displayed.
    Activity Displays the activity for each chain step, such as the date and time when the plugin ran, the changeset where it ran, and the associated review. Some plugins include a link to a web page with additional details.
    Changesets Lists the changesets consumed by this run.
    Requests Lists the requests related to this run.
    Changes Lists the files that have changed since the previous run. Click a file to open it in a code browser.
    Variables

    Lists the variables defined for the chain.

    If no chain variables were defined, the tab is not displayed.
    Dependency Vulnerabilities

    For chains with dependencies, displays a list of security issues discovered in third-party dependencies.

    If no vulnerabilities were found, the tab is not displayed.
    Dependencies

    For chains with dependencies, displays a list of third-party files included in the chain.

    If there are no dependencies, the tab is not displayed.
    Artifacts

    Displays information about captured artifacts.

    Artifacts captured to a vault: Click a package to view it inside the vault to which it was deployed. For details about reviewing packages, see Review and approve packages.

    Note: PulseUno captures artifact information only if the chain used temporary system credentials to authenticate to the vault during deployment. For details, see Built-in variables.

  7. To run this chain again on the same changeset, click Re-run.

  8. To override the default retention policy and keep the chain run details, click Keep Forever. For details about retention policies, see Create retention policies.

Back to top

See also: