Quality Clouds allows you to connect Git repositories to scan configuration and source code, enabling continuous quality analysis across development environments.
By connecting your repository, Quality Clouds can analyze code against best practices and quality rules, helping teams detect issues early in the development lifecycle.
What It’s Used For #
Connecting a Git repository enables Quality Clouds to scan source code and configuration files directly from version control systems.
This allows development teams to:
- Identify quality issues and vulnerabilities early
- Monitor code quality across branches and environments
- Compare feature branches against reference branches
Supported Git providers include:
- GitHub / GitLab
- Bitbucket
- Azure DevOps / Visual Studio
Prerequisites #
Before configuring the repository connection, ensure you have:
- Quality Clouds Admin portal credentials
- Git repository information
- Authentication credentials:
- Git User ID and Password
- Personal Access Token (recommended) with read access to the repository
Supported Authentication Methods
Quality Clouds supports the following authentication options:
User Credentials
- Username and password for the Git repository
Personal Access Token (Recommended)
- Token used instead of a password
- Must provide read access to the repository
- Recommended for improved security and compatibility with modern Git providers
Set Up a Git Repository Instance #
To scan a repository, you must create a Git-based instance in the Quality Clouds portal.
Steps:
- Log in to the Quality Clouds portal.
- Access the Admin Portal from the right menu.
- Navigate to the Instances section.
- Select the ServiceNow tab (if using multiple SaaS platforms).
- Click Add.
- Select the Project the instance belongs to, or create a new project.
- Choose Git Repository and complete the required fields.
Instance Configuration Fields
| Field | Description |
| Description | Short identifier for the instance |
| Environment | Environment type (Dev, QA, UAT, Prod) |
| Git Flavor | Git provider (GitHub, GitLab, Bitbucket, Azure DevOps) |
| Git Repository URL | Full repository URL |
| Branch | Name of the reference branch to scan |
Feature Branch Scanning
Feature Branch scanning are enabled by default to analyze specific development branches.
- The scan compares the feature branch with the reference branch
- Only the differences between branches are analyzed
- The branch name is requested when launching the scan
Authentication Configuration #
Option 1 — User Credentials
| Field | Description |
| User ID | Git repository username |
| Password | Git account password |
Note: Some Git providers may restrict password authentication.
Option 2 — Personal Access Token (Recommended)
| Field | Description |
| User ID | Git username or service account |
| Password | Personal Access Token |
The token must provide read access to the repository.
Additional Optional Settings #
| Field | Description |
| Go-live Date | Date when the instance became active |
| First Scan Date | Date of the initial scan |
| Tags | Labels used to organize and identify instances |
