Version Control
Last updated
Last updated
This section helps the user to get a private token to access multiple versions of the Data Science workflows, scripts, and models.
Click the Version Control option from the Configurations menu.
The Version Control page opens.
Provide the required Version Control Information:
Select a Module using the drop-down option (The supported modules are datascience, Pipeline, Dashboard, ApiService, DsLabs)
Host address of the GitLab link.
Token Type: The user can select one option out of the given choices. Based on the selected Token Type option the configuration fields may display.
User Credentials: By selecting this option the Admin needs to pass an email address of the GIT Lab and valid password. The user gets to enable a checkbox to generate a private token (as displayed in the below-given image).
Private Token: By selecting this option the Admin needs to pass the Private Token (as displayed in the below-given image).
The fields provides under the More Information heading are pre-selected. The Entity Type, Work Space Name, and Entity Type get displayed based on the selected module. The supported entity extension is '.baf'.
Click the Test option after providing the required Version Control Information.
A notification message appears to confirm about the successful authentication.
There will appear two more fields:
Select a GIT Lab Project from the drop-down menu.
Based on the selected GIT Lab project, it will list all the branches. Select a branch from the drop-down menu.
After providing the required information for Version Control the Save option gets enabled. Click the Save option.
A success message appears to inform the version control update.
Please Note: After the Version Control gets saved, and the confirmation message appears all the fields become blank once again.