This page explains how to configure the Migration option for a module through New Version Control.
Transfer the files from the source location to the target location within a software platform using the Migration option. The user can configure the migration-related settings using the New Version Control admin option.
The supported modules for the migration are listed below:
API Service
Dashboard
DS Lab (Repo Sync Projects, Notebook & Model)
Pipeline
Story (Report)
Select the New Version Control option from Configurations under the Admin module.
The Version Control Information form opens.
Select the Migration option from the first dropdown.
All supported modules will be listed under the Select a Module drop-down which are supporting the Version Control functionality. (E.g., Dashboard is selected in the given image).
Select the Git type as either GitLab or GitHub.
Provide the Host information.
Provide the Token Key.
Click on the Test button.
Select the Project
Select a Branch where files need to be stored on the VCS.
Configure the More Information fields.
Provide the following information:
Entity App
Work Space Name
Entity Extension
Entity Type
Click the Test option.
A notification message appears to inform about the successful authentication.
The Save option gets enabled. Click the Save option.
A configuration message appears and the configuration for the New Version Control gets saved.
BDB provides Versioning option as a simplified process to track changes for the various modules to ensure efficient development and enhance collaboration for effective code management.
Version control systems like Git provide a robust set of features to ensure efficient and reliable software development. They enhance collaboration, enable effective code management, and simplify the process of tracking changes, thereby contributing to the overall quality and maintainability of the software.
Version Control feature helps the users to maintain a copy of component versions in the Version Control System (Gitlab | GitHub repository). The user can also pull a specific version from the Version Control System after some versions are pushed there. The supported modules for the versioning are as follows:
Dataset
Data as API
Data Store
Dashboard
DS Lab ( Project & Notebook)
Pipeline script
Select the New Version Control option from the Configurations under the Admin module.
The Version Control information form opens.
Select the Version option from the first dropdown.
All supported modules will be listed under the Select a Module drop-down which supports the Version Control functionality. (E.g., Dashboard is selected in the given image).
Select Git type as either GitLab or GitHub.
Provide the Host information.
Provide the Token Key.
Click on the Test button.
Select the Project
Select a Branch where files need to be stored on the VCS.
Configure the More Information fields.
Provide the following information:
Entity App
Work Space Name
Entity Extension
Entity Type
Click the Test option.
A notification message appears to inform about the successful authentication.
The Save option gets enabled. Click the Save option.
A configuration message appears and the configuration for the Version Control gets saved.
Please Note:
The user needs to set up the associated module configuration for each component.
The configuration fields may vary based on selecting the Select field and the Token Type information.
