Appearance

Repository Management ​

The Repository Management dashboard is your command center for configuring, monitoring, and governing source code analysis. From here, you can control how the analysis engine treats your code and how findings are handled across your team.

1. Execution & Monitoring ​

Triggering a Scan ​

Scan History & Detailed Logs ​

Investigate past performance or troubleshoot scan failures by selecting Scan History from the context menu. You will see a chronological log of every engine stage.

Real-time Log Example:

text
17:52:30 | Scan Request Queued
17:53:03 | Scanner Started
17:53:20 | Parsing Completed (C++)
17:55:29 | Issue Detection Started (SCA)
17:56:38 | INFO: Total 1062 code issues were found.
17:56:50 | Scan Completed

2. Advanced Scan Configuration ​

Tailor the analysis engine to ignore noise and focus on critical paths.

  • Exclusions & Inclusions: Define file patterns (e.g., **/vendor/** or **/dist/**) to skip third-party code or focus on specific modules.
  • Code Checker Configuration: Enable or disable specific engines (e.g., PMD, Checkstyle, Spotbugs) and customize rules for languages like Java, C++, and more.
  • Pipeline Script: Access pre-configured scripts for seamless CI/CD integration.
  • 👉 CLI Scanner Reference & Command Options →

3. Governance & Workflow ​

Suppression Workflows ​

Control how issues are "silenced" based on your team's hierarchy:

  • Enabled (Approval Required): Developers request suppression; a Lead/Admin must approve or reject it.
  • Disabled (Direct): Users can suppress issues immediately without an approval chain.
  • Disallow Suppression: Completely lock down the repository—no issues can be suppressed or grouped.

Cross-Repository Linking ​

If you have multiple repositories sharing the same source (e.g., a "Core" repo mirrored in two projects), link them. Scanning one will automatically import all suppressions and groupings from the other, preventing duplicate triage work.

Quality Gate Profiles ​

Assign a specific Quality Gate Profile to enforce strict Pass/Fail thresholds (e.g., "Block merge if Critical Issues > 0").

4. Lifecycle & Maintenance ​

Edit Repository ​

Modify metadata or migrate repository types. You can change the Name, Language, or even switch the Type (e.g., migrating a ZIP upload to a live Git URL).

Critical Operations ​

ActionOverviewData Impact
Get RepoUIDRetrieve the unique identifier for API/CLI calls.Informational
Unlink RepoRemove the repo from the project view while keeping data.History Preserved
Delete RepoPermanently wipe the repository and its entire history.Permanent Loss

Identifying the RepoUID ​

The RepoUID is required for all CLI integrations.

Unlinking a Repository ​

Use this to hide a repository from a project without losing your scan history.

Deleting a Repository ​

Caution: This action is irreversible and aborts any ongoing scans.

5. External Integrations ​

Issue Tracker Integration (Jira) ​

Bridge the gap between finding a bug and fixing it.

  • Setup: Go to Repository Settings → Issue Tracking.
  • Workflow: Create and sync tickets directly from the UI into your task manager.
  • 👉 Issue Tracking Setup Guide →

Supported Sources ​

  • Cloud/Git: GitHub, Bitbucket, GitLab, Azure DevOps.
  • Legacy: SVN, RTC (Rational Team Concert).
  • Local/Custom: ZIP uploads, Remote CLI, and VCA (Version Control Accounts).

Best Practices ​

  • Incremental Scans: Use for rapid PR feedback.
  • Full Scans: Schedule weekly on the main branch for a total quality "health check."
  • Path Pruning: Keep exclusion lists current to ensure scan times remain fast and relevant.

Project Setup & Configuration ​

Analysis & Scanning ​

Quality Governance ​

Integration & Automation ​

Access Control ​

Copyright © 2025 BrowserStack