...

Download the Kyvos CICD Utility.

Export Utility

Anchor
ExportUtility ExportUtility

Prerequisites

To use the Export utility, you must have the following.

...

Below are several scenarios to export multiple semantic models, relationships, and dataset entities in single export using the config.json if the respective values are set as Y.

• #Appendix

  Export single entity present from a single folder

  • "CUBEDETAILS": { "Folder1" : [ “Cube1”] }

  • "DRDDETAILS": { "Folder1" : [ “DRD1”] }

  • "RFDETAILS": { "Folder1" : [ “RF1”] }

  • "WBDETAILS": { "Folder1" : [ “WB1”] }

• Export multiple entities from a single folder

  • "CUBEDETAILS": { "Folder1" : [ “Cube1”, “Cube2”] }

  • "DRDDETAILS ": { "Folder1" : [ “DRD1”, “DRD2”] }

  • "RFDETAILS": { "Folder1" : [ “RF1”, “RF2”] }

  • "WBDETAILS": { "Folder1" : [ “WB1”, “WB2”] }

• Export multiple entities from multiple folders

  • "CUBEDETAILS": { "Folder1" : [ “Cube1”,”Cube2”], “Folder2” : [“Cube3” ] }

  • "DRDDETAILS ": { "Folder1" : [ “DRD1”,” DRD2”], “Folder2” : [“DRD3” ] }

  • "RFDETAILS": { "Folder1" : [ “RF1”,” RF2”], “Folder2” : [“RF3” ] }

  • "WBDETAILS": { "Folder1" : [ “WB1”,” WB2”], “Folder2” : [“WB3” ] }

• Export All entities from one or more folders

  • "CUBEDETAILS": { "Folder1" : [], “Folder2” : [] }

  • "DRDDETAILS ": { "Folder1" : [], “Folder2” : [] }

  • “RFDETAILS": { "Folder1" : [], “Folder2” : [] }

  • “WBDETAILS": { "Folder1" : [], “Folder2” : [] }

• Export single/multiple entities from ROOT (when entities are not a part of any folder)

  • "CUBEDETAILS": { "ROOT" : [ “Cube4”, “Cube5”] }

  • "DRDDETAILS ": { "ROOT" : [ “DRD4”, “DRD5”] }

  • "RFDETAILS": { "ROOT" : [ “RF4”, “RF5”] }

  • "WBDETAILS": { "ROOT" : [ “WB4”, “WB5”] }

• Export ALL entities, which includes all entities at ROOT and all folders with all entities

  • “CUBEDETAILS": { }

  • “DRDDETAILS ": { }

  • “RFDETAILS": { }

  • “WBDETAILS": { }

...

1. Browse to the Export_Executor folder and double-click the exe file to execute it.
   

   Image RemovedImage Added

2. The Export utility starts executing. Once the export is complete, you can check the execution logs in the output folder.
   The following figure shows a snippet of the Export Utility execution.

   Image RemovedImage Added

3. If the GITPUSH parameter is set as Y in the Config file, then all the entity XML files will get exported to the Git Feature branch in the following order.

   1. A GIT PULL is performed from the feature branch specified in the config file. So that the remote and local repository (GITRepo) are in sync.

   2. The entities are exported to the GITRepo folder from Kyvos, which is a local repository clone of the Git repository, as shown in the following figure.

      Image RemovedImage Added

   3. Entities are then pushed to the Git feature branch, as shown in the following figure. We have used the working feature branch in this case.
      

      Image RemovedImage Added

4. If the GITPUSH parameter is set as N in the Config file, then the entities are directly exported to the Output folder in the Export No GIT PULL and GIT PUSH will be performed in this case.

...

1. In case the Jenkins job is not created and configured, see the section Creating new Project in Jenkins.

2. In case the Jenkins job is not Integrated with Git Repository, see the section Git settings to integrate with Jenkins.

3. In case the Git connection is not created in Jenkins, see the section Creating Git Connection in Jenkins.

Once the above steps are completed, you can execute the Deploy Utility using any of the following methods.

...

You can also deploy entities using the DeployKyvosEntities.py Python script. In this case, the Deploy Utility is triggered by executing the following commands using the Jenkins jobs.

...

The Personal Access Token is required for authentication of Export Utility with Git. You are required to provide this in the Export Utility config file, as explained in the Export Utility section.

To create a Personal Access Token in Git, perform the following steps.

1. In your Git account, navigate to Edit Profile.

2. On the left pane, click Access Tokens.

   

3. Give the token a Descriptive name, select the Scopes which define the access for the Personal tokens, and then click the Create personal access token. A token is generated. 

...

1. In Manage Jenkins > System Configuration > Configure System and then follow these steps.

   1. In the Git section, check the Enable authentication for '/project' end-point

   2. Click Add, then choose Jenkins Credential Provider.

   3. Choose Git API token as the token type.

   4. Enter the Git personal access token's value in the API Token field and click Add.

   5. Enter the Git server's URL in the Git host URL.

      Image RemovedImage Added

   6. Click Test Connection, ensuring the connection is successful before proceeding.

      Image RemovedImage Added

   7. After testing the connection, enter the connection name and save.

      Image RemovedImage Added

Anchor
CreatingNewProject CreatingNewProject

Creating new project in Jenkins

...

1. Login to your Jenkins account and click New Item from the top left of your dashboard.

2. Enter the name of the item you want to create, select Freestyle project, and click OK. The project is created.
   

   Image RemovedImage Added

3. Navigate to the newly created project and select the Configure option, as shown in the following figure.
   

   Image RemovedImage Added

4. On the General tab, click on Git Connection and select the connection.

   Image RemovedImage Added

5. On the Source Code Management tab, select the Git option on the left and provide your Git Repository URL and Credentials in the corresponding fields.

6. Change the Branch Specifier as shown in the below screenshot */main this is the branch we intend to build using Jenkins. In this example, we have selected main to Build.

7. Select the Repository Browser as Auto.

8. In Additional Behaviours, select the Wipe out repository & force clone option to erase the local repository and clone the fresh repository every time to avoid inconsistency.

   Image RemovedImage Added

9. On the Build Triggers tab, select Build when a change is pushed to Git

10. It is used to execute the Deploy Utility as soon entities are merged from the Feature branch to the Master branch in Git repository mentioned in Jenkins above.
    

    Image RemovedImage Added

Anchor
Creatingsecrettoken Creatingsecrettoken

Creating secret token in Jenkins

1. Click Advanced to generate the secret token required for configuring Webhooks.

   Image RemovedImage Added

2. On the Build Steps tab, select the Execute Window batch command and enter the command (explained in the Deploy Utility section) to execute the Utility.

   

3. Click the Save button to save your changes.

...

1. In your Git Account, select the repository you want to integrate with Jenkins and go to Settings.

2. Select the Webhooks option from the left pane.

   Image RemovedImage Added

3. In the URL, enter the URL and append “/project/project name” to this URL, as shown in the figure below, and enter the secret token. To generate the secret token, check the section Creating secret token in Jenkins). For example, http://localhost:8080/project/Git

   Image RemovedImage Added

4. Select Push events in the trigger and then click Add webhook.