Learn how multi-level JFrog repository support enables more precise onboarding and efficient data management.
DevOps Intelligence enhances its JFrog integration to support multi-level repository structures, enabling more precise onboarding and improved data visibility. This reduces unnecessary data processing and introduces UI and guidance changes to streamline adoption. Users can now select specific levels within a repository, such as submodules and folders instead of onboarding entire repositories, providing greater flexibility for shared environments, minimizing unnecessary data ingestion and ensuring accurate artifact attribution.
Onboard a technical service
This process allows users to navigate repository structures, select the appropriate level (folder or image) and onboard only the required components instead of entire repositories.
Key considerations:
The same UI (the table with expandable levels) appears in every tool or phase where JFrog is used. This includes areas like: Vulnerability scan, License scan and other JFrog integrations.
Regardless of where the feature or tool is accessed, the user can:
See the same repository structure.
Navigate folders in the same way.
Select images or folders using the same logic.
The experience is standardized across tools, so users do not need to relearn the process for each feature.
The following steps guide you through onboarding a technical service using the updated JFrog integration experience:
Go to the
Kyndryl Bridge DevOps Console
page.
From the left navigation, select
Kyndryl Services
.
Locate
Tool Chain & Pipeline Observability
and navigate to
DevOps Intelligence
.
Scroll through the available sections and locate
Settings & Utilities
.
Select
Application Configurations
to open and manage application-level settings.
Locate the application name, select the three dots on the right and navigate to
Onboard Technical Service
.
Complete the required fields on the Onboard Technical Service page:
Application Name
: This is auto-populated based on your previous selection.
DevOps Phase
: Secure
Secure Categories
: Container Vulnerability Scan
Tool Engine
: JFrog
Select the
connection
: JFrog-DI
Select the
repository
.
Select the
submodule
.
9. Click
Onboard
to complete the process.
Selecting a submodule
The table displays the repository structure in multiple levels instead of a single submodule view, allowing users to navigate deeper into the hierarchy and choose specific folders or images to onboard as needed.
Consider the following before selecting a submodule:
Child entries that are images or tags should be selected separately. Instead, select the parent folder to onboard all underlying items.
Select either a folder (repository or submodule) or an item within it, such as an image or microservice and expand rows to navigate deeper into the hierarchy.
Expand a folder and continue expanding to see individual images inside it. Some entries, such as image tags or certain child elements, should not be selected individually. A warning message appears to guide users to select the correct level instead.
Avoid onboarding unnecessary images and support cases where multiple teams share the same repository.
Items that are already configured appear in the interface and cannot be selected again in the repositories table. If more granular onboarding is required, the existing configuration must be removed before onboarding again using the updated structure.