Table of Contents

Creating a repository

Connector repository

In order to create a new repository for a connector, click the Create repository button in the Protocols tab. This will open the Create New Repository pop-up window, where you can provide the name of the vendor and data source.

Note

The name of the data source should start with the name of the vendor. If it does not, the following error will be shown in the status bar: (ERROR) Data Source does not start with: <VendorName>.


SLC SE Repository Manager: Creating a repository

  • In case no version of this protocol exists on SVN yet, when the create button is clicked, the following message will be shown:


    SLC SE Repository Manager: Creation confirmation

    When you click Yes, a new Git repository will be created on the server with the specified name. The repository will automatically be cloned to your local path after the remote repository has been created by Gerrit.

    Every new repository contains the following files:

    • .gitignore: This file makes it possible to automatically keep certain files from being tracked (such as build output).

    • Jenkinsfile: This file is used by the Jenkins build server.

  • In case some versions of the specified protocol already exist on SVN, the SLC SE Repository Manager tool will create a new Git repository with branches corresponding with the ranges that exist on SVN. For each version of the protocol on SVN, a tag will be created in the Git repository.


    SLC SE Repository Manager: Conversion confirmation

    Consider the following example: Suppose you need to create a new version of the Generic Database protocol. On SVN, the following versions exist of this protocol:

    • 1.0.0.1

    • 1.0.0.2

    • 1.0.0.3

    • …

    • 1.0.0.8

    • 2.0.0.1

    • 2.0.0.2

    • 2.0.0.3

    This means that when you create a new Git repository for this protocol, the SLC SE Repository Manager tool will create a new Git repository with two branches, "1.0.0.X" and "2.0.0.X", and it will also create tags for each version of the protocol.

    Each version of this repository will have a "fromSvn" folder containing the content that was found on SVN for that version. This will typically be the protocol.xml file and the checklist.

Important

Once a Git repository has been created for a protocol, this repository should be used for creating new versions. This means new versions must no longer be manually added on SVN. On SVN, you can verify whether this protocol has been migrated to Git already by checking for the presence of a "ConvertedToGit.txt" text file in a version folder.

Other repository types

The SLC SE Repo Manager has different tabs for other repository types: Visios, Custom Solutions, Functions, Automation Scripts, Dashboards, Examples, Packages, and Files.


SLC SE Repository Manager: Creating a Files repository with Constraint, Category, and Name

To create a new repository, click the Create repository button in the corresponding tab. This will open the Create New Repository pop-up window, where you can provide the following information:

  • Constraint: Defines the visibility of the Catalog item. Select one of the following options:
    • Customers: The repository is created specifically for one specific customer. The Catalog item will be private.
    • Generic: The repository can be reused. The Catalog item will be public. This does not apply to dashboards; those are currently private Catalog items.
    • Internal: The repository is not meant to be published on its own. It is part of an install package or is exclusively for internal use by Skyline. The Catalog item will be private.
  • Category: The category beneath the constraint.
  • Name: The user-friendly name of the repository.
Propose changes